Re: NSTemporaryDirectory() && Windows

[Richard Frith-Macdonald]

On 2005-05-11 12:30:06 +0100 Marc Brünink <mbruen@smartsoft.de> wrote:

>>>> 2. A method of NSString which converts 8.3 pathnames to long ones.
>> 
>> Again, 'why' ....windows provides one for you, and it would have no use 
>> whatsoever outside of the windows environment, so adding it to GNUstep 
>> would be useless bloat.
> 
> Because sometimes you need to convert 8.3 too long pathnames. Perhaps you 
> want to display them  in a nice format or perhaps you want to write  a 
> configuration file for a third party program (<- I want to do this). Actually 
> it doesn't matter why some people need this. I just think 
> stringByStandardizingPath should handle this.

Well, that's an entirely separate issue to NSTemporaryDirectory().
The job of stringByStandardizingPath  is to standardize to a consistent format  
... I'm not sure whether it should convert windows paths to the longest, most 
readable format (what you seem to want), or the most portable format (which 
would do the opposite of what you want), but I think it should probably do one 
or the other under windows.  My first inclination is to say it should do the 
opposite of what you want ... and try to make the most portable format, but I'm 
not sure about that, perhaps the lonmg format works everywhere under windows 
now?  Certainly the focus of the method (standardising the path) is on making 
it usable rather than pretty.

> Currently 
> stringByStandardizingPath thinks ~C/DOKUME~1/ADMINI~1/.... is an invalid 
> path, which is simply wrong!

Well, I think the current CVS code would expect a path C:/DOKUME~1/ADMINI~1/ as 
there is new experimental code in place which handles the  C: drive specifier, 
and I'm expecting to change things that create paths to use the C: format 
rather than ~C for the internal format of strings.
I'm not sure what earlier code would have done.