in reply to syntax for URI of files?

Well, I think that Perl6 really need the URI. Everyone that have tried to use Perl5 on Mac saw the problem, and the difference between file systems don't stop here.

About the use of file://c:/foo instead of file://c|/foo, weel I think that the both will work, since we have many programms that use them today.

About the use of reserved characters in file names, well, we can't tell to someone that use a OS to not use some symbol because in other doesn't work! In other words, in theory we need to can put "any" symbol in file names. To do that, how about use the %HH, that every body know in the URI? We already use that for spaces, %20.

This is a inportant point, since when we talk about Perl6 we say Parrot, and Parrot is not only for Perl, is a VM for many languages. And I think that some upgrades to the rolls of URI can be made, since URI was defined a "long time ago" and was tested very well, and now we can know the best options to choice.

Graciliano M. P.
"The creativity is the expression of the liberty".

Replies are listed 'Best First'.
Re: Re: syntax for URI of files?
by John M. Dlugosz (Monsignor) on Mar 07, 2003 at 16:59 UTC
    In the URI::File module, it shows 
      Unix                  URI
  ----------            ------------------
  foo/bar      <==>     foo/bar
  /foo/bar     <==>     file:/foo/bar
  /foo/bar     <==      file://localhost/foo/bar
  file:         ==>     ./file:
  <undef>      <==      file:/fo%00/bar
  /            <==>     file:/

    [download]
    that is, one slash only if no host, but doesn't show three slashes for that same case. But, I thought the leading // after the file: meant that the rest of the name uses the slash-separated hiarachy, otherwise is opaque, so one slash isn't right? But that wouldn't explain relative URL syntax.

    If we have %HH syntax, why map : to | at all? It's not like anyone types filename urls in that syntax.

[reply]
[d/l]

In Section Seekers of Perl Wisdom