2012/7/12 Sean P. DeNigris <sean@clipperadams.com>
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
Hello, Good you found this thread. I have no time to see deeper what happens with current FS state. But I think my questions not influence current design changes. So, I am very interesting what you thing about all of that?