Hi David & Sven, On Thu, 14 Feb 2019 at 07:46, Sven Van Caekenberghe <sven@stfx.eu> wrote:

David,

...

On 14 Feb 2019, at 03:56, David Richards <david.i.richards.iii@gmail.com> wrote:

Hi community,

Consider:

| file | file := FileLocator workingDirectory . file fullName . "==> '/Users/dr/Documents/Pharo/images/Study (Pharo 7.0 - 64bit stable)'" file pathSegments . "==> #()"

How do we obtain path segments for the working directory?

Is this an edge case where pathSegments does not return a semantically consistent value?

Thanks David

A FileLocator is a bit special, it is usable, but not yet fully realised, more abstract.

You can use resolve. Consider:

FileLocator home pathString. "'/Users/sven'"

FileLocator home resolve pathSegments. "#('Users' 'sven')"

What Sven wrote is, of course, correct. But this is also an edge case: FileLocator workingDirectory resolve pathSegments. "#()" The reason in this case is because the directory is stored as a RelativePath. A RelativePath is resolved against the working directory, which in this case is the same thing, so no movement is required, and an empty path is used. You can also try: FileLocator workingDirectory asAbsolute pathSegments. " #('home' 'alistair' 'pharo8' 'pharo64.04')" Just for added confusion, FileLocator class>>workingDirectory is also a special case. Most of the methods in the origins protocol return an instance of FileLocator. But FileLocator class>>workingDirectory returns an instance of FileReference. HTH, Alistair

Hi Sven, Your second example expression fails for 'workingDirectory': FileLocator workingDirectory resolve pathSegments ==> #() It works fine for FileLocator home but not for FileLocator workingDirectory . Your first expression will produce the desired result, if en*source*lled with syntactimancy: FileLocator workingDirectory pathString asFileReference pathSegments This smells a lot like an edge case to me. But perhaps it is the Way of Smalltalk. Thanks David On Wed, 13 Feb 2019 at 22:46, Sven Van Caekenberghe <sven@stfx.eu> wrote:

David,

...

On 14 Feb 2019, at 03:56, David Richards <david.i.richards.iii@gmail.com> wrote:

Hi community,

Consider:

| file | file := FileLocator workingDirectory . file fullName . "==> '/Users/dr/Documents/Pharo/images/Study (Pharo 7.0 - 64bit stable)'" file pathSegments . "==> #()"

How do we obtain path segments for the working directory?

Is this an edge case where pathSegments does not return a semantically consistent value?

Thanks David

A FileLocator is a bit special, it is usable, but not yet fully realised, more abstract.

You can use resolve. Consider:

FileLocator home pathString. "'/Users/sven'"

FileLocator home resolve pathSegments. "#('Users' 'sven')"

HTH,

Sven

Perfect. Many thanks. On Thu, 14 Feb 2019 at 05:14, Sven Van Caekenberghe <sven@stfx.eu> wrote:

...

On 14 Feb 2019, at 13:55, David Richards <david.i.richards.iii@gmail.com> wrote:

Hi Sven,

Your second example expression fails for 'workingDirectory':

FileLocator workingDirectory resolve pathSegments ==> #()

It works fine for FileLocator home but not for FileLocator workingDirectory .

Your first expression will produce the desired result, if ensourcelled with syntactimancy:

FileLocator workingDirectory pathString asFileReference pathSegments

This smells a lot like an edge case to me. But perhaps it is the Way of Smalltalk.

Like Alistair said, it should be

FileLocator workingDirectory asAbsolute pathSegments.

because it is a relative path.

...

Thanks David

On Wed, 13 Feb 2019 at 22:46, Sven Van Caekenberghe <sven@stfx.eu> wrote: David,

...

On 14 Feb 2019, at 03:56, David Richards < david.i.richards.iii@gmail.com> wrote:

Hi community,

Consider:

| file | file := FileLocator workingDirectory . file fullName . "==> '/Users/dr/Documents/Pharo/images/Study (Pharo 7.0 - 64bit stable)'" file pathSegments . "==> #()"

How do we obtain path segments for the working directory?

Is this an edge case where pathSegments does not return a semantically consistent value?

Thanks David

A FileLocator is a bit special, it is usable, but not yet fully realised, more abstract.

You can use resolve. Consider:

FileLocator home pathString. "'/Users/sven'"

FileLocator home resolve pathSegments. "#('Users' 'sven')"

HTH,

Sven