[Pharo-project] UUIDs not so unique
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
On 07/20/2011 03:59 PM, Torsten Bergmann wrote:
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) ;)
Did the bug eat your code? Cheers Philippe
Em 20-07-2011 11:29, Philippe Marschall escreveu:
On 07/20/2011 03:59 PM, Torsten Bergmann wrote:
(...) Did the bug eat your code? Are you a professional developer? If so you must have got stuck in bugs before. MS bugs, Linux bugs, Mac OS bugs, compiler bugs, jdk bugs, library bugs...
I have been stuck on bugs. And I can tell you for sure that pharo/squeak communities are extremely responsive. You point a bug and solution comes in hand. I can not tell the same about "commercial software manufacturers" (just try "online support" from the major OS supplier in the market... or file a bug and track how long it takes to be fixed). And remember, contrary to pharo, you have to purchase "visual this or that" in order to use such "marvelous development suite". Even in open source communities: you have a trouble with Linux kernel you fill a report in bugzilla and it takes sometimes years to be closed. So, I can't understand: a) your over reaction b) your insistence in a subject that has proved itself exhausted. By the way, the bug didn't "eat your code". Just put the primitive expression inside double quotes and your code will work all right (supposing it's correct). Regards, CdAB
Cheers Philippe
On 07/20/2011 05:08 PM, Casimiro de Almeida Barreto wrote:
Em 20-07-2011 11:29, Philippe Marschall escreveu:
On 07/20/2011 03:59 PM, Torsten Bergmann wrote:
(...) Did the bug eat your code? Are you a professional developer? If so you must have got stuck in bugs before. MS bugs, Linux bugs, Mac OS bugs, compiler bugs, jdk bugs, library bugs...
I have been stuck on bugs. And I can tell you for sure that pharo/squeak communities are extremely responsive. You point a bug and solution comes in hand. I can not tell the same about "commercial software manufacturers" (just try "online support" from the major OS supplier in the market... or file a bug and track how long it takes to be fixed). And remember, contrary to pharo, you have to purchase "visual this or that" in order to use such "marvelous development suite". Even in open source communities: you have a trouble with Linux kernel you fill a report in bugzilla and it takes sometimes years to be closed. So, I can't understand:
a) your over reaction
It ate my code.
b) your insistence in a subject that has proved itself exhausted.
By the way, the bug didn't "eat your code". Just put the primitive expression inside double quotes and your code will work all right (supposing it's correct).
Yeah right. I already have an SCM repository (Seaside 3) with several versions with the same UUID. First I have to write a tool that asses the damage which means pulling all my open source code including the full Seaside 3 repository from SqueakSource and search for duplicate UUIDs. Then I have to hope and pray that the corruption doesn't go too far back. Then for all the broken packages I have to load the last correct code. Then for each of them I have to load the latest code without Monticello and commit it with a different version number. Then I have to remove all broken the versions with screws everybody who already used them as ancestors. Cheers Philippe
participants (3)
-
Casimiro de Almeida Barreto -
Philippe Marschall -
Torsten Bergmann