Normally when you enter a bug fix in the issue I will close it when it
is harvested/refused....
I will do the classbuilder related ones now.
Stef
On Sep 12, 2008, at 7:18 PM, Noury Bouraqadi wrote:
Stéf,
On 11 sept. 08, at 21:32, Noury Bouraqadi wrote:
On 11 sept. 08, at 09:44, Stéphane Ducasse wrote:
Hi noury
I started to harvest your fixes and I learned something :)
when most of your fixes are about extending or changing a package
just publish a new version of that package. This way I can use the
merge tool
and be much more efficient, do not create a specific package with
specific class extension
for it else I have to modify everything by hand.
This sounds like a cleaner way indeed.
If you didn't finish harvesting it, I can split different changes
as you suggest.
Did you harvested my previous fixes ?
Cause I added an extra bug fix (attached) to the class builder to
avoid the creation of "zombie" classes (classes not in the
SystemDictionary => Memory leak) when class variable names are
lowercase. The test
BTW, where one can check to see if a package has been harvested?
Noury
------------------------------------------------------------------
Dr. Noury Bouraqadi - Enseignant/Chercheur
Responsable de l'enseignement de l'informatique
ARMINES - Ecole des Mines de Douai - Dept. I.A.
http://vst.ensm-douai.fr/noury
European Smalltalk Users Group Board
http://www.esug.org
------------------------------------------------------------------
<fixClassVarsVarlidation-Noury12sept2008.cs>
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
