FileTree export format on Windows

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

FileTree export format on Windows

Peter Uhnak

Hi,

 

I just ran into a quite nasty issue when using GitFileTree on Windows with the FileTree export format.

 

Apparently there are reserved names on Windows:

 

> CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9

 

And I had an “aux” and “aux:” methods in Pharo, which were attempted to be exported as “aux.st” and “aux..st”, but silently failed.

 

There are also other rules https://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx#naming_conventions which might break binary selectors (I haven’t tried those).

 

I am not sure how I am supposed to deal with this, but assuming Pharo wants to support all platforms, this should be resolved in some manner; in the meantime I will use some alternative name.

 

Thanks,

Peter

Reply | Threaded
Open this post in threaded view
|

Re: FileTree export format on Windows

Sven Van Caekenberghe-2

> On 19 Aug 2016, at 09:36, Peter Uhnák <[hidden email]> wrote:
>
> Hi,
>  
> I just ran into a quite nasty issue when using GitFileTree on Windows with the FileTree export format.
>  
> Apparently there are reserved names on Windows:
>  
> > CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9
>  
> And I had an “aux” and “aux:” methods in Pharo, which were attempted to be exported as “aux.st” and “aux..st”, but silently failed.

The silently fails part is really bad !

> There are also other rules https://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx#naming_conventions which might break binary selectors (I haven’t tried those).
>  
> I am not sure how I am supposed to deal with this, but assuming Pharo wants to support all platforms, this should be resolved in some manner; in the meantime I will use some alternative name.
>  
> Thanks,
> Peter