> > It's gonna be slow. The index file fo every part of the
> > path must be read to determine the next piece.
>
> Yes, but it should be faster than clicking through by hand.
True.
> > reb://REBOL.com/sites/anton/gui/
>
> > But it should be easy to work this into the desktop patch,
> > using just a lit-path for now instead of a new pseudo-protocol.
>
> Hmmm. I'm sure it's possible, but how would you grab all the path at
> the console...
>
> >> x: func [n][probe n]
> >> x /a-path/blah
> /a-path
> == /blah
>
> ?
>
> --
> Carl Read
Like this:
x: func [n][probe n]
x 'a-path/blah
== a-path/blah
I've decided that I wouldn't be ultimately happy with using
a lit-path! anyway, so I'd check out the protocol idea.
All we need to do is distinguish from url!, so we can use a
string! or a block! with the path in it.
But your example leads to an "interesting thing":
to-lit-path %/a-path/blah
== '/a-path//blah ; <- double slash
and note also
to-lit-path %/a-path/blah/dog
== '/a-path//blah//dog ; <- two double slashes
Is this a bug, or just escapism?
Has anyone else reported this?
Anton.
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
