🚀 go-pugleaf

In some cases it's so you can hide the exact implementation from
either yourself or another programmer who's using your classes.  As in
if you're just giving them an implementation of a set, but you don't
want them to know how you've implemented it - they can only access it
through the interface.

Plus they let you do multiple inheritance (sort of).

Myself, I like 'em, but I'm just another poor uni student who's too
used to mucking about with header files in C.

Danny Smith

On Fri, 14 Apr 2000 17:18:55 +1000, Ross Vumbaca <rossv@au.net.fl>
wrote:

>Hi,
>
>Alan wrote:
> 
>> Can some one tell me why & when you would use an interface?
>
>If you want multiple (perhaps different approach/performing)
>implementations to one standardardised interface.. Hmm I dunno what..
>You raised a good question (for me anyway)
>
>Regards,
>
>Ross..
> 
>-- 
>*TO E-MAIL ME: Reverse the order of the domain name in my e-mail
>address.*
>
>Ross Vumbaca, a 'poor' Uni student at USyd.edu.au
>http://www.fl.net.au/~rossv, e-mail: rossv@fl dot net dot au (fix this
>if you e-mail me!)
>
>Running on an Amiga 3000, NEC M700 17" thingy,
>030/25, ECS, 8Mb Fast, 2Mb Chip, SCSI HDD's (never mind their size)
>Kickstart 3.1 (40.68), OS 3.5, Linux 2.0 (RedHat 5.1) and an Opalvision
>card -
>("Designed in Australia", and keeping the Zorro bus populated).
>--