Hi Phillipe, software changes and (new) bugs can appear - thats life and happens independent from Pharo or other technology.
There is a simple rule: "If it is broken we should fix it" and I would add "and make sure it wont bug us anymore again". At least we should in minimum find such bugs before a release. Therefore attached is a simple test case that is green on my VM and should be red on your VM. Let's integrate it into Pharo, you already know the usual procedure to open an issue and I'm sure the Pharo team and VM maintainers will take care. Simple as that ... Side note about recommending technologies and bug fixing: I once found a bug in Swing, others already reported it and it is still after years(!) not fixed: http://astares.blogspot.com/2007/01/disappointing-swing.html So I have to wait and wait since I cant fix Swing myself... If this error would be in Smalltalk I would easily be able to change it until it is officially fixed. So in Smalltalk I can easily move on and it gives me the good feeling of beeing in control. Still Java is more recomended than Smalltalk. Why? Because in the hopefully rare case a project really fails or is late it could not have been the problem of choosing an exotic technology since others use and recommend Java too (sometimes known as the herd instinct) ;) Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
UUIDPrimitivesTest-testUniqueness.st
Description: Binary data
