Sun, 01 Feb 2009 03:08:43 +0100 changed #bitAt:
Claus Gittinger <cg@exept.de> [Sun, 01 Feb 2009 03:08:43 +0100] rev 11502
changed #bitAt:
Sun, 01 Feb 2009 03:08:32 +0100 changed #bitAt:
Claus Gittinger <cg@exept.de> [Sun, 01 Feb 2009 03:08:32 +0100] rev 11501
changed #bitAt:
Sun, 01 Feb 2009 03:03:52 +0100 changed #bitAt:
Claus Gittinger <cg@exept.de> [Sun, 01 Feb 2009 03:03:52 +0100] rev 11500
changed #bitAt:
Sun, 01 Feb 2009 03:01:58 +0100 comment
Claus Gittinger <cg@exept.de> [Sun, 01 Feb 2009 03:01:58 +0100] rev 11499
comment
Thu, 29 Jan 2009 21:21:46 +0100 comment
Claus Gittinger <cg@exept.de> [Thu, 29 Jan 2009 21:21:46 +0100] rev 11498
comment
Mon, 26 Jan 2009 15:42:58 +0100 changed #fileInNextChunkNotifying:passChunk:silent:
Stefan Vogel <sv@exept.de> [Mon, 26 Jan 2009 15:42:58 +0100] rev 11497
changed #fileInNextChunkNotifying:passChunk:silent: When evaluating a expression while filing in, do not raise error on undeclared variable or namespace. We want to evaluate some code like: aClass loadLibrariesOnSuccess:[Namespace:Class start]. whe Namespace and Class is define *after* the libraries have been loaded.
Mon, 26 Jan 2009 09:53:00 +0100 prime stuff
Claus Gittinger <cg@exept.de> [Mon, 26 Jan 2009 09:53:00 +0100] rev 11496
prime stuff
Sat, 24 Jan 2009 22:32:16 +0100 subtile bug in primesUpTo: - did not include the limit,
Claus Gittinger <cg@exept.de> [Sat, 24 Jan 2009 22:32:16 +0100] rev 11495
subtile bug in primesUpTo: - did not include the limit, if it was a prime (i.e. upTo:n was actually upTo:n-1 if n was itself prime) This only happened for primes above 25000 (i.e. in largePrimesUpTo)
Sat, 24 Jan 2009 22:05:09 +0100 *** empty log message ***
Claus Gittinger <cg@exept.de> [Sat, 24 Jan 2009 22:05:09 +0100] rev 11494
*** empty log message ***
Sat, 24 Jan 2009 21:40:24 +0100 +bitCount
Claus Gittinger <cg@exept.de> [Sat, 24 Jan 2009 21:40:24 +0100] rev 11493
+bitCount
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 tip