>>>> Menu Bar >>>> -------- >>>> Squeak now has a standard menu bar to make it easier to discover its >>>> contents for new users, replacing the World menu as the prime source for >>>> launching tools and other activities. >>>> >>>> Compiler >>>> -------- >>>> Support for literal ByteArray syntax has been added. Byte arrays can now >>>> be written as #[1 2 3 "..."] instead of #(1 2 3) asByteArray avoiding the >>>> need for conversion and a more compact default representation. >> we got that since long time ago >> > > Yes, I picked the method from Pharo :)
:) I really wonder what would be squeak if you would not push it ;-D > >>>> Numbers >>>> ------- >>>> Some prime related changed: Integer>>isPrime is now a deterministic test, >>>> Integer>>isProbablyPrime a probabilistic variant. >> I think that andres changes were introduced. But apparently not. >> I will do that. Strange >> > > I think Leventes just picked Andres change... This is strange because I thought I integrated that. I will redo it. > >>>> Intger>>highBit and Integer>>lowBit have been sped up significantly. >> This is in >> > > Yes, though I cached 8bits in trunk instead of 4bits in Pharo and > initila mantis report. This is strange because I check the code and it looked similar. I will recheck later. > >> >>>> >>>> CRLF Handling >>>> ------------- >>>> CR and LF are now treated interchangeably in rendering. Both cause a line >>>> break and both are not displayed. Various line related methods have been >>>> updated to deal with both CR and LF. >> >> I imagine that this were fixes of nicolas >> > > Only the line splitting stuff is in Pharo (it was started in Pharo). > I did not port the transparent displaying of line feeds to Pharo yet. > Are you interested ? what is it? > >>>> Collections >>>> ----------- >>>> Dictionary is no longer a subclass of Set. HashedCollection is the new >>>> superclass for both Set and Dictionary. Conversion of OrderedCollection >>>> and SortedCollection to Arrays has been sped up significantly. >> This is cool...... >> We definitively should look at that. >> > > Yes, it should be ported to Pharo, I see no reason of divergence there. Yes and I like the fast in the sentence :) _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
