On 14 November 2010 19:45, Matt Emson wrote:
> methods. We used them much as one would with in .Net these days. More about
> light public interfaces, encapsulation and delegation rather than ref
> counting and such.
This is how I use interfaces too. I never to COM programming as such,
but do you
On 14 November 2010 19:49, Martin Schreiber wrote:
>>
> Reference counted interfaces need compiler magic AFAIK.
Indeed, you are correct.
--
Regards,
- Graeme -
___
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net:8080/
On 14 Nov 2010, at 13:16, Graeme Geldenhuys wrote:
> On 14 November 2010 14:18, Sven Barth wrote:
>> IInterface and IUnknown are the same in Delphi 7 as well as they are in FPC
>> (although they are aliased the other way round, but that doesn't matter).
>
>
> So then comes the big question — wh
On Sunday, 14. November 2010 17.30:13 Graeme Geldenhuys wrote:
> Under all other OSes, (which don't have COM), FPC should default to
> CORBA style interfaces, where IInterface is non-COM - same as what was
> done in Kylix. What's the point of have COM style interface on
> non-Windows platforms any
Graeme Geldenhuys schrieb:
On 14 November 2010 18:44, Florian Klaempfl wrote:
... and as soon as we do such a logical decision, you start whining, whining
about the bad fpc developers destroying your business plans.
Bo hoo... It's called being able to maintain code in the long run.
Oh, I for
On 14 November 2010 18:44, Florian Klaempfl wrote:
>
> ... and as soon as we do such a logical decision, you start whining, whining
> about the bad fpc developers destroying your business plans.
Bo hoo... It's called being able to maintain code in the long run.
Keep adding one hack after the next
On 14.11.2010 17:30, Graeme Geldenhuys wrote:
On 14 November 2010 17:25, Sven Barth wrote:
Besides think about the following:
Let's say IInterface would be changed to be the base ancestor type for Corba
interfaces. What about existing classes that implement IInterface (which
currently declares
Graeme Geldenhuys schrieb:
FPC's designs should stay logical
and clean, and it's up to the developers to maintain their application
code and fixe such bad/broken code.
... and as soon as we do such a logical decision, you start whining,
whining about the bad fpc developers destroying your b
On 14 November 2010 17:25, Sven Barth wrote:
> Besides think about the following:
>
> Let's say IInterface would be changed to be the base ancestor type for Corba
> interfaces. What about existing classes that implement IInterface (which
> currently declares QueryInterface, AddRef and Release, caus
On 14 November 2010 15:58, Marco van de Voort wrote:
>
> Please leave IInterface alone. It took me a week of work to let the current
> IInterface=IUnknown alias propagate properly in fpdoc's internal structures
> :-)
:-) I can't say I saw that one coming.
--
Regards,
- Graeme -
_
On 14.11.2010 14:58, Marco van de Voort wrote:
In our previous episode, Graeme Geldenhuys said:
This is exactly what I am saying IInterface is a non-COM interface in
Kylix
Please leave IInterface alone. It took me a week of work to let the current
IInterface=IUnknown alias propagate properly i
In our previous episode, Graeme Geldenhuys said:
> This is exactly what I am saying IInterface is a non-COM interface in
> Kylix
Please leave IInterface alone. It took me a week of work to let the current
IInterface=IUnknown alias propagate properly in fpdoc's internal structures :-)
___
On 14 November 2010 15:36, Sven Barth wrote:
>
> Ask Borland why they decided to do it that way... perhaps they wanted a
> common ancestor for they case they ever decide to use non COM interfaces...
> (I can only guess here)
This is exactly what I am saying IInterface is a non-COM interface in
Ky
On 14.11.2010 14:16, Graeme Geldenhuys wrote:
On 14 November 2010 14:18, Sven Barth wrote:
IInterface and IUnknown are the same in Delphi 7 as well as they are in FPC
(although they are aliased the other way round, but that doesn't matter).
So then comes the big question — why have IInterface
On 14 November 2010 14:18, Sven Barth wrote:
> IInterface and IUnknown are the same in Delphi 7 as well as they are in FPC
> (although they are aliased the other way round, but that doesn't matter).
So then comes the big question — why have IInterface then, if it is
exactly the same as IUnknown,
On 14.11.2010 13:03, Graeme Geldenhuys wrote:
On 14 November 2010 13:03, Sven Barth wrote:
It's Delphi compatible:
http://docwiki.embarcadero.com/VCL/XE/en/System.IInterface
So yes, it seems to be a COM interface even in Delphi 7+ (I don't know about
Kylix though).
I don't know that the lat
On 14 November 2010 13:03, Sven Barth wrote:
>
> It's Delphi compatible:
> http://docwiki.embarcadero.com/VCL/XE/en/System.IInterface
>
> So yes, it seems to be a COM interface even in Delphi 7+ (I don't know about
> Kylix though).
I don't know that the latest Embarcadero docs say, but IInterface
On 14.11.2010 11:52, Graeme Geldenhuys wrote:
Hi,
Below is an example of two interfaces I declared. Trying to implement
them on a TObject subclass, I got a compiler error that IUnkown was
not implemented in my subclass. In all units I defined {$interfaces
corba}
Eventually I found out that I ha
18 matches
Mail list logo
