I feel dirty every time, but FS doesn't make this piece of a reference's identity explicit. Would it be valuable to have FSFileReference and FSDirectoryReference subclasses? It would certainly make my code cleaner as I could then double dispatch without conditionals.
we should record what you find so that we can fix it.
On Nov 3, 2011, at 2:25 PM, Sean P. DeNigris wrote:
> Sean P. DeNigris wrote:
>> Would it be valuable to have FSFileReference and FSDirectoryReference
> Another weird ramification of FSReference's identity ambiguity is, on a
> reference to an existing file:
> * #allChildren -> anArray containing only the file itself
> * children -> an error
> View this message in context: http://forum.world.st/FSReference-tp3985640p3985818.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com.