[Vm-dev] Extending primitiveDirectoryEntry

[Alistair Grant]

Hi Tim,

On Mon, Apr 24, 2017 at 09:46:59AM -0700, tim Rowledge wrote:
>  
> You might need to check your assumptions here. Different OSs have
> different ideas about what - or even *if* - a current working
> directory means. 
> 
> You also need to consider the *intent* of such paths. Setting a
> default to the directory in which the image was found may or may not
> make sense; what if it is a default image installed in some place that
> is not intended for general user storage?  What if it is reached via
> an alias so any attempt to find the parent directory results in a very
> strange seeming result?
> 
> Caching such things can be fraught with pain too. Is it plausible that
> the actual working directory you thought was at
> wibble/foo/gerbil/cardboard-tube has been reset since you found that?
> What if the user or some administration process moves things around
> whilst you are running?

Yep.  Anyway, changing the definition now would likely break lots of
code.

I might look at adding a method that returns the parent process working
directory (if one exists in Pharo, I haven't found it).

Thanks,
Alistair