Collection interfaces (Was: New to OO concepts - re-usability)

Topmind topmind at technologist.com
Sun Feb 25 20:32:51 EST 2001


> "Topmind" <topmind at technologist.com> wrote
> in message news:MPG.150312ceb68f1ada98969f at news.earthlink.net...
> >
> > This is a sore point with me. To me it seems silly (artificial)
> > to split collection handling into categories (stacks, sets, trees, etc.).
> > If needs change from one to another or a combo, then you are hosed
> > with a non-fitting interface.
> 
> Yes, and so OO language provide an advantage here. Collection classes
> in these languages are accessible through common interfaces. You don't
> care how they are implemented, you only care about the interface.
> 


You mean something like SQL or ODBC?

And, this crap that only OO can do 
implimentation-hiding interfaces is
pure propaganda.

(Note that I am talking about using
the interfaces, not making DB
engines or whatnot.)


> > Shape up!
> 
> Yeah!
> 
> --
> Patrick Logan
> mailto:patrickdlogan at home.com
> 

-tmind-



More information about the Python-list mailing list