Hi guys,

nothing terrible, just some comments on paths and file references

I found today myself doing in a method:

^ (AbsolutePath withAll: anAbsolutePath path segments, aRelativePathFilename segments) asFileReference exists.

To put a relative path on top of an absolute path because lack of a better option

But shouldn't this be doable?

absolutePath / relativePath / aFilename

We're half an inch of that syntax sugar

I saw that / expects only strings, but we can take advantage of file references, wouldn't make more sense to expect both strings or file references?

and then there is this

'' asFileReference = '/' asFileReference. true 

doesn't feel right

thoughts?

sebastian

o/