Re: [Pharo-project] FileSystem. Possible FSReference rename

Denis Kudriashov wrote
> 
> I think FSLocator and FSReference are same objects:
> FSReference = fileSystem + path
> FSLocator = "some origin object" + path.
> 
> I think "some origin object" can be implemented as special
> FSRelativeFileSystem. And fileLocator became fileReference.
> 
> Now in "FSLocator vmDirectory" "some origin object"  is symbol. And
> FileLocator>>resolve method perform some complex stuff through FSResolver
> hierarchy logic.
> 
> What is purpose of FSResolver hierarchy?
> What is purpose of #resolve: and #resolve methods? Why so many classes (in
> FileSystem) implement it: FSLocator, FSReferece, FSPath, FSFileSystem,
> FSResolver?

>From Issue 6333: FileSystem refactoring
"- cleaned up FileLocator / FileReference hierarchy
- use FileLocators wherever possible"

Cami, what do you think about Denis's point?

Sean

--
View this message in context: http://forum.world.st/FileSystem-Possible-FSReference-rename-tp3317375p4639654.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.