Thierry Goubier wrote > Once you > generate automatically, it's easy to hit them :P
Besides the hard limits IIRC I also ran into weird unexpected issues like really long methods slowing Nautilus down to a crawl. Is there a library that can effectively take source code and break it up into a reasonable set of methods to avoid these issues? I think this could also be useful in a lot of places e.g. STON. I've been using a trick to distribute "data" which changes often in development but is read-only when deployed; I work with the live model and serialize to method source (like we do with icons I guess). I've had to use different strategies e.g. I favor STON but when porting to Amber, there is no STON, so I serialize to source code. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Microframeworks-was-Re-Thank-you-so-much-for-Pharo-3-0-tp4786128p4786222.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
