<br><br><div class="gmail_quote">On Fri, Nov 20, 2009 at 8:37 PM, Colin Putney <span dir="ltr"><<a href="mailto:cputney@wiresong.ca">cputney@wiresong.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
On 20-Nov-09, at 8:23 PM, Eliot Miranda wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Colin,<br>
<br>
you say nothing in the tutorial about Windows drive letters. I imagine 26 upper or lower case selectors could provide e.g.<br>
<br>
FSPath C / 'plonk' / 'feep' => C:\plonk\feep<br>
</blockquote>
<br></div>
You're right, I should have a section on how things work on Windows.<br>
<br>
The above example isn't quite right, because Windows drives are actually separate filesystems, in contrast to Unix's single-rooted filesystem. So the twenty six selectors should be on FSReference. It's a great idea though, thanks!<br>
</blockquote><div><br></div><div>I wonder how useful that distinction is. Remember in unix different filesystems can occur within the same namespace, e.g. mounting something on /usr or /home or /mnt etc. Even though the Windows drive letters do map to different file systems they are still a single namespace. Yes there will be operations that will fail across file systems (rename) but there will still be operations within the same filesystem that will fail (e.g. copy to a write-protected directory entry).</div>
<div><br></div><div>If FSReference can be done without and added as a whistle for special purpose use then all the better. Something minimal, effective and easy to use is the sweet spot.</div><div><br></div><div>BTW, one thing that always frustrated me about the VW implementation was not being able to proceed through certain exceptions. The classic example is implementing find in the presence of unreadable directories where you want to be able to proceed across the read protect rather than aborting the entire find. i.e. there's some utility on a path such as allChildrenDo: upon which is built find like facilities. At the find client level one wants to be able to wrap an exception handler around the allChildrenDo: invocation that will e.g. report errors to the transcript but proceed without aborting.</div>
<div><br></div><div>So a good set of use cases is making it easy to implement some basic unix utilities, mv, cp, find, cat etc.</div><div><br></div><div>I'm probably attempting to teach you to suck eggs, forgive me :)</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><font color="#888888">
<br>
Colin<br>
<br>
<br>
<br>
</font></blockquote></div><br>