Well, Peter posted here his results on his Windows XP and it is slow on his PC, too.
About those non-latin characters... lots of these benchmarks are made on compilation of ASCII characters as far as I know, without our project ever loaded. I tested whole loading also on Roassal2 package where I don't expect non-ASCII characters (any way to find out for sure?). Sven Van Caekenberghe-2 wrote > Jan, > > I find it rather hard to believe you are the only Windows users for who > #flush is slow. This is such a fundamental operation that it should have > been caught earlier. Remember that the Pharo code itself is cross platform > identical. Anyway, that is how I feel it. > > Just an idea: does your source code contain non-Latin-1 characters (i.e. > WideStrings), even a single one ? Maybe your name itself (the č). > > Sven -- View this message in context: http://forum.world.st/Slow-compilation-on-one-of-my-Windows-PCs-tp4834668p4835508.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
