I think you are correct about that being a bad change, but there is more wrong than just that. There are IPv6-specific calls that are not protected by subsequent tests on #useOldNetwork. Further, the IPv6 code does not work correctly, so many of us appear to need to override #useOldNetwork to always return true. I make that change in #useOldNetwork rather than #initialize.
Bill -----Original Message----- From: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Miguel Enrique Cobá Martinez Sent: Thursday, January 28, 2010 5:00 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Bug in NetNameResolver on PharoCore 10508? El mié, 27-01-2010 a las 16:01 -0600, Miguel Enrique Cobá Martinez escribió: > El mié, 27-01-2010 a las 21:07 +0100, Mariano Martinez Peck escribió: > > > > > > > Add it. So that not to forget. If it is not a bug, we just close it > > and that's all. > > > > > http://code.google.com/p/pharo/issues/detail?id=1884 > > I think that get to the source of the problem. Is the change of UseOldNetwork from false to true in the last images. I added a comment (http://code.google.com/p/pharo/issues/detail?id=1884#c4) to the issue with a procedure to reproduce the problem in old images (that worked ok) and to correct the problem in the last image (that doesn't work). Can you please test it and decide if it is right to revert to the old version of NetNameRelease class>>initializeNetwork? Any comment welcome Thanks -- Miguel Cobá http://miguel.leugim.com.mx _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
