I am developing MathsOntologie under Pharo 2.0 beta, and testing it under Pharo 1.4; when the test is OK I distribute MathsOntologie with Pharo 1.4 as "all in one". Don't know if it is the best way to do but I became used to it... By the way, I am ashamed that I never made a unit test... Also, when I wanted to translate in French the method "add: anObject times: aNumber" to a Collection, I found that it didn't work, so I created it with something like Collection>add: anObject times: aNumber aNumber timesRepeat: [self add: anObject]. I don't know if it was intended or a bug, and and did not find it very difficult to create this method but I asked myself why this method did not work. And I could not test it afterwards because I could not update Pharo 2.0 beta (conflicts between consecutive updates); I have to download Pharo 2.0 and transfer MathsOntologie inside the new version; I just did not have the time... Alain On Thu, Mar 28, 2013 at 12:34 PM, Goubier Thierry <thierry.goubier@cea.fr>wrote:
Le 27/03/2013 15:24, Esteban Lorenzano a écrit :
Hi,
Here in Pharo headquarters we are shock that there are just 10 new bugs reported for 2.0 after the release... So... I wonder... is that because we made a really cool release, or just because nobody is using it?
Cheers, Esteban
Hi,
I've started to load things in 2.0 (SmaCC, some of my current work) but then the current work caught me back and I'm finishing it on 1.4 at the moment.
Oh, I think I also stopped because I couldn't load FileTree in 2.0 and I need it for a git-based workflow.
Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95