[Pharo-project] SocketAddress>>printOn: - a (potentially serious) defect?

SocketAddress>>printOn: looks like it does some questionable things, but I am fuzzy on what exactly is happening and what should be done about it. My thought would be that the address should have name and number aspects, that resolving would do the respective lookups, and that inspecting should not attempt the lookups. Do you agree? How broken is the implementation? I cant' say that I am thrilled about addresses being inherited from ByteArray - I suppose it can happily be the address and have an iv for the name, but what if one knows the name and later wants to resolve the number? This sounds like a job for a subclass of Object with named variables. Anybody agree or disagree? Bill