From: Brett L. <wak...@ea...> - 2005-03-03 06:46:59
|
I think this is a good direction to take. Are you able to submit some code to move us in that direction? ---Brett. *********** REPLY SEPARATOR *********** On 3/2/2005 at 10:12 PM Iain Adams using ia...@co...= declared: >I suggested in a previous post using interfaces for primary datatype >definitions: one example of how this is done can be found in the Java >Collections framework. Here List is an interface which has a number of >implementation classes, which differ in their internal representations: >ArrayList LinkedList, etc. StockMarket.getIpoPile() has a return type of >ArrayList - this class should be free to change its list representation >without an API change, which can be achieved by declaring the method to >return a List. Personally, I would also make the member variable ipoPile= be >type List, and initialise it as a 'new ArrayList()' in the first instance. > >Iain. > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick >_______________________________________________ >Rails-devel mailing list >Rai...@li... >https://lists.sourceforge.net/lists/listinfo/rails-devel ********** REPLY SEPARATOR END ********** This message sent with 100% recycled electrons. |