And of course we're interested in feedback and ideas on how to proceed with the situation. A few comments I got at ESUG: - do an ecosystem analysis to see what parts of the API are most used (and therefore sensitive to evolution) - check the cost of String allocations; YBuffer was an effort in avoiding useless copying of string data http://www.squeaksource.com/ajp
On 19 Jul 2015, at 04:20, Sean P. DeNigris <sean@clipperadams.com> wrote:
Luc Fabresse wrote
Here they are
Got them, thanks :)
----- Cheers, Sean -- View this message in context: http://forum.world.st/IWST-Papers-tp4838128p4838139.html Sent from the ESUG mailing list archive at Nabble.com.
_______________________________________________ Esug-list mailing list Esug-list@lists.esug.org http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org
-- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet