+1 > Well, you can save a bit more, if you scan a whole image literals and > unify them. > This could be userful for tidying up the image size. > > > Probably yes, but that's not the point I guess. I just wanted to show that > the current method doesn't really save much. Unifying the literals in the > image is dangerous, because literal strings are not immutable (and they > shouldn't be IMHO).
+ 10 I would love to have immutability bit. > So that could lead to random errors if a method is modifying a shared string > literal. This can of aliasing is bad, it mixes semantics and implementation. I hope that we will be able to fix that with Opal. Stef _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
