Hi Eliot,

I'm sorry if my tone was critical, I did not mean it that way. As I said, these are useful convenience methods.

Dave

On 2024-05-07 23:18, Eliot Miranda wrote:

 

On Mon, May 6, 2024 at 5:29 PM <lewis@mail.msen.com> wrote:

Just for reference, if you have OSProcess/CommandShell loaded you may want to look at classes ShellSyntax and ShellSyntaxTestCase, especially method category 'path name expansion'.

The #currentDirectoryNickname and #parentDirectoryNickname methods are useful convenience methods, but they are really based on Unix shell syntax conventions so we would not want too much of this logic leaking into the base image.

 

".." means the same thing in the win32 filesystem as it does in Unix.  I seriously doubt any filesystem in which shells are used doesn't have a nickname for the parent directory.  The image framework allows a different nickname to be used. I don't see the harm myself.

 

This kind of thing feels to me like "asking forgiveness" is easier than not using it, in that we can fix usage later when we encounter a filesystem t6hat breaks the mould.  That's better than struggling to do without common and useful facilities.

$0.02,

Dave