Thanks for the info :) >> yeah, i think its protocol could have two entry points: >> - #add: for adding an object to list >> - #addLink: for linking a link to list >> >> so, that, #add: always creates a new instance of ValueLink , without >> asking object to do #asLink >> and then sends #addLink: , which does the rest. > I don't quite see the appeal in an approach which both has a more complicated > protocol, and is backwards-incompatible. > > Cheers, > Henry > > PS. We DID consider other possible solutions before deciding to add "yet > another" as... method to Object >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
