> Ok, give a poor C++ programmer a hint... what are we talking about here?
> <G>
I think you lot call them "pure virtual classes" - ie a class with
no implementation. In Delphi, you can inherit from more than one of them,
which is a big advantage.
> Specifically, I've seen many definitions for 'interfaces', but none of
> them seems to quite fit the discussion. Does some kind soul out there
> feel like enlightening me?
:)
N
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
- [DUG]: Interfaces Sandeep
- Re: [DUG]: Interfaces Neven MacEwan
- Re: [DUG]: Interfaces Sandeep
- Re: [DUG]: Interfaces Neven MacEwan
- Re: [DUG]: Interfaces Sandeep
- RE: [DUG]: Interfaces Max Nilson
- RE: [DUG]: Interfaces Nahum Wild
- Re[2]: [DUG]: Interfaces paul . mckenzie
- Re: RE: [DUG]: Interfaces Corey Murtagh
- Re: [DUG]: Interfaces Nic Wise
- Re: [DUG]: Interfaces Nic Wise
- Re: [DUG]: Interfaces Neven MacEwan
- Re: RE: [DUG]: Interfaces Nello Sestini
- RE: RE: [DUG]: Interfaces Colin Fraser
- RE: RE: [DUG]: Interfaces Max Nilson
- Re: RE: [DUG]: Interfaces Sandeep
- RE: RE: [DUG]: Interfaces Max Nilson
- Re: RE: [DUG]: Interfaces Neven MacEwan
- RE: RE: [DUG]: Interfaces Max Nilson
- Re: RE: [DUG]: Interfaces David Brennan
