Re: NSMessagePortNameServerWin32.m error

[Wim Oudshoorn]

Richard Frith-Macdonald <richard@tiptree.demon.co.uk> writes:

> On 31 Jan 2007, at 16:25, Wim Oudshoorn wrote:

>> but apparently the method +[NSError _last] does not exist.
>
> That method is implemented in base/Source/Additions/GSCategories.m
>
> Did something go wrong with your build of the base library somehow?

I think I know what went wrong, we have patched an older GNUstep
version with your changes and in our version there is no _last 
in GSCategories.  So that was my mistake.

Futher, the issue I am now chasing is in our code, but caused
by the fact that fileSystemRepresentation on windows returns 
strings in double byte encoding.

Final point, I am still a little worried about the 
NSMessagePortNameServerWin32 class.  My worries have no
practical impact for us, so I might not investigate it deeper.

Worry:  The connection name is used on windows as the name
of a mailslot.  Because mailslots names are modelled after filenames
I am not sure if there are any implicit restrictions on connection names.
For example I would not be surprised if connection names like:

    *
    ..\a
    a and a\b 


Ah well, back to work.

Wim Oudshoorn.