On Sun, Jul 19, 2009 at 4:45 PM, Damien Cassou<damien.cas...@gmail.com> wrote: >> However, there are problems on Windows too - in fact, I suspect the >> following would be a defect on any platform: #localHostName uses >> #primHostNameSize (ipv6 specific, right??) "unprotected." Looking at the >> other methods, it should check #useOldNetwork, though I am confused about >> how it should act based on the result. Any suggestions? > > I confirm. I also have a problem with NetNameResolver on Windows. > > NetNameResolver localHostAddress > > fail in #primHostNameSize. > > http://code.google.com/p/pharo/issues/detail?id=961
by bsch...@anest.ufl.edu: Network problem on windows. Primitive failed. http://code.google.com/p/pharo/issues/detail?id=961 I suspect the real problem is IPv6 vs. 4, not an OS dependence. #initializeNetwork uses #primHostName size as a sentinel for the new network. The code suggests to me that it is expected to fail at times, and so should never be called "unprotected" as it is in #localHostName. We probably do NOT want to put #on:do: around ever send, but instead use #useOldNetwork to write code that will not blow up on IPv4. That's *if* I have guessed correctly about the true nature of the defect. Anyone? -- Bill -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
