Re: Issue 2176 in pharo: Integrated DirectoryEntry>>attributes

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Issue 2176 in pharo: Integrated DirectoryEntry>>attributes

pharo

Comment #5 on issue 2176 by [hidden email]: Integrated  
DirectoryEntry>>attributes
http://code.google.com/p/pharo/issues/detail?id=2176

Nice! I needed and implemented DirectoryEntryFile>>extension myself and  
then saw this. But does it make sense in DirectoryEntry? What is the  
extension of a DirectoryEntryDirectory? How about:

DirectoryEntryFile>>extension
       ^ FileDirectory extensionFor: self name


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 2176 in pharo: Integrated DirectoryEntry>>attributes

pharo

Comment #6 on issue 2176 by [hidden email]: Integrated  
DirectoryEntry>>attributes
http://code.google.com/p/pharo/issues/detail?id=2176

The question is: do we change the old File code if we now have FS?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 2176 in pharo: Integrated DirectoryEntry>>attributes

pharo
Updates:
        Status: Invalid

Comment #7 on issue 2176 by [hidden email]: Integrated  
DirectoryEntry>>attributes
http://code.google.com/p/pharo/issues/detail?id=2176

I think we should not care to change the old Filesystem code


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker