Stef (correctly) does not like filling Object with methods that have no business there. IMHO, one thing that is worse is the horrible level of needless subclassing in Squeak. However dubious (or simply avoidable) it might be to intermingle an ip address and a port, it is much worse to subclass the whole mess from a byte array :( I have hit several similar kinds of bugs in the process of trying to sort out the IPv6 changes. Port numbers are orthogonal to addresses, and addresses come in name and number. We would do well to follow Dolphin in having an address with two aspects, either of which can be set and other lazily resolved. Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Miguel Enrique Cobá Martinez Sent: Wednesday, January 13, 2010 5:02 PM To: Pharo Subject: Re: [Pharo-project] [ANN] Metacello configuration of OSProcess El mié, 13-01-2010 a las 15:52 -0600, Miguel Enrique Cobá Martinez escribió: I ran the tests in PharoCore 10506 and got 4 failures: AioEventHandlerTestCase>>#testSocketExceptionEvent AioEventHandlerTestCase>>#testSocketReadableEvent AioEventHandlerTestCase>>#testSocketReadableEventWithMaskNotSet AioEventHandlerTestCase>>#testSuspendAioForSocketReadableEvent All of them caused by ByteArray(Object)>>doesNotUnderstand: #port: in: Socket>>connectTo:port: Cheers -- 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