Why? The tests are green.
When you change a complete compiler and AST then it is a lot of changes.
Then each time you changes a comment you change the timestamp so…..
Now 30 is stable since months.
Stef
PS: you know what is frightening is when you have a bug that arrives only after
2 weeks on
Pharo4Stef wrote:
Why? The tests are green.
When you change a complete compiler and AST then it is a lot of changes.
Then each time you changes a comment you change the timestamp so…..
Now 30 is stable since months.
Stef
PS: you know what is frightening is when you have a bug that arrives
On Thu, Feb 20, 2014 at 2:49 AM, Esteban A. Maringolo
emaring...@gmail.com wrote:
20% of change in Quantity terms is a lot!
that's really a lot and is a bit frightening.
--
Damien Cassou
http://damiencassou.seasidehosting.st
Success is the ability to go from one failure to another without
Here is a simple calculation (that probably can be improved by the reflection
or Moose aficionados) to estimate the amount of change between Pharo 2.0 and
3.0 by counting the number of methods in the image that have a timestamp later
than 2.0's release date: these should be new or modified.
2014-02-19 19:30 GMT-03:00 Sven Van Caekenberghe s...@stfx.eu:
Here is a simple calculation (that probably can be improved by the reflection
or Moose aficionados) to estimate the amount of change between Pharo 2.0 and
3.0 by counting the number of methods in the image that have a timestamp
