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 had to remove the (IInterface) heritage
from my
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
On 14 November 2010 13:03, Sven Barth pascaldra...@googlemail.com 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
For example if there are two Interface : IinterfaceA,IinterfaceB
can I implement these two interface in one class?
Thanks
pingyu
___
fpc-pascal maillist -
On 14.11.2010 13:03, Graeme Geldenhuys wrote:
On 14 November 2010 13:03, Sven Barthpascaldra...@googlemail.com 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).
On 14.11.2010 13:08, yu ping wrote:
For example if there are two Interface : IinterfaceA,IinterfaceB
can I implement these two interface in one class?
Yes, you can. Take the following example:
type
IInterfaceA = interface
procedure A;
end;
IInterfaceB = interface
procedure
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 November 2010 14:08, yu ping wrote:
For example if there are two Interface : IinterfaceA,IinterfaceB
can I implement these two interface in one class?
Yes you can, but be warned, Interfaces doesn't seem to be a high
priority feature in FPC - I don't think many here use Interfaces.
There
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
Martin Schreiber wrote:
Hi,
MSEide+MSEgui version 2.4 for FPC 2.4.2 has been released:
https://developer.berlios.de/project/showfiles.php?group_id=11520
Questions and bug reports please to mailing list:
https://lists.berlios.de/mailman/listinfo/mseide-msegui-talk
NNTP gateway:
On 14 November 2010 15:36, Sven Barth pascaldra...@googlemail.com 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
In our previous episode, Paul Breneman said:
This is a new page with FPC 2.4.2 and fpGUI:
http://www.turbocontrol.com/easyfpgui.htm
I'd like to set up a similar page for MSEgui (and maybe for MSEide as
well). Please contact me off-list about this.
Btw, you might want to scrap the
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 :-)
Paul Breneman wrote:
I'd like to set up a similar page for MSEgui (and maybe for MSEide as
well). Please contact me off-list about this.
Done.
Martin
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
Marco van de Voort wrote:
In our previous episode, Paul Breneman said:
This is a new page with FPC 2.4.2 and fpGUI:
http://www.turbocontrol.com/easyfpgui.htm
I'd like to set up a similar page for MSEgui (and maybe for MSEide as
well). Please contact me off-list about this.
Btw, you
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
Does TObject have all the capabilities of TComponent apart from things like
streaming and being used from the IDE component palette?
I want to create an object which has all the capabilities like getting and
setting properties, and I want to know whether I need to inherit from
TObject or from
On 14 November 2010 15:58, Marco van de Voort mar...@stack.nl 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 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, cause
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
Hi Everybody,
On 14 November 2010 16:31, Jonas Maebe wrote:
Please don't spread FUD. There are several projects that make heavy use of
interfaces that work fine with FPC (e.g. Zeoslib). Yes, interface delegation
is not finished (other than that, interfaces work fine afaik)
Let me just
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
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
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
On 14.11.2010 17:49, Graeme Geldenhuys wrote:
* incomplete delegation (non existent in FPC 2.4.2)
I haven't used this for quite a long time, so I can't test it just
now... what are you missing?
* No name resolution (function aliases) of conflicting interfaces
Ehhh... the
Sven Barth schrieb:
* No name resolution (function aliases) of conflicting interfaces
Ehhh... the following code compiles with 2.4.2 and even 2.4.0:
Typical FUD tactics: mix something people know being true with something
wrong and they believe you the wrong statement.
var
t:
On 14.11.2010 18:17, Florian Klaempfl wrote:
var
t: TMyInterfacedObject;
i: IMyInterface;
begin
t := TMyInterfacedObject.Create;
try
i := t;
t.Foo;
i.Foo;
finally
t.Free;
end;
end.
source end
Output is:
output begin
Foo
Bar
An unhandled exception occurred at $08056B71 :
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
On 14 Nov 2010, at 13:16, Graeme Geldenhuys graemeg.li...@gmail.com 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
On 14 November 2010 19:11, Sven Barth pascaldra...@googlemail.com wrote:
* No name resolution (function aliases) of conflicting interfaces
Ehhh... the following code compiles with 2.4.2 and even 2.4.0:
My apologies then, I must not have seen the announcement. I also
looked in my ref.pdf
On 14 November 2010 19:49, Martin Schreiber mse00...@gmail.com wrote:
Reference counted interfaces need compiler magic AFAIK.
Indeed, you are correct.
--
Regards,
- Graeme -
___
fpGUI - a cross-platform Free Pascal GUI toolkit
On 14 November 2010 19:45, Matt Emson memson.li...@googlemail.com 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
On Sun, 14 Nov 2010, Frank Church wrote:
Does TObject have all the capabilities of TComponent apart from things like
streaming and being used from the IDE component palette?
I want to create an object which has all the capabilities like getting and
setting properties, and I want to know
I suspect the reason is that the object still has a refCount of 1 when you free
it and this code raises the exception:
procedure TInterfacedObject.BeforeDestruction;
begin
if frefcount0 then
HandleError(204);
end;
You should never free an interfaced object
On 14 Nov 2010, at 17:49, Graeme Geldenhuys wrote:
By all means, if it will make you feel
better/happier, then why not simply unsubscribe or band my from all
FPC and Lazarus related mailing lists while you are at it.
It has nothing to do with with how I feel, although I can't say that I
FWIW, both interface delegation (implements) and method aliasing have been
supported in FPC for at least 2 years (we first tested/used them in January
2009 with FPC 2.2.2 which was released in August 2008).
* We have used method aliasing extensively - it appears to behave the same as
36 matches
Mail list logo
