Re: RFC 100 (v1) Embed full URI support into Perl

2000-08-16 Thread Nathan Wiger
> So, what's so portable about file:// URLs again? How do they magically > know that //c/ means / on UNIX? What do they do with //z/? This is only one example. I'm not sure it's the best way. It's definitely not the only way. Chaim asked: > Or for that matter "file://u/frankeh/Projects" become

Re: RFC 100 (v1) Embed full URI support into Perl

2000-08-16 Thread Gisle Aas
Nathan Wiger <[EMAIL PROTECTED]> writes: > With URI support, you still have to contort a little, but not as much. > Here's some better examples from an email I sent earlier: > >$fo = open "file://c/docs/personal"; > ># Unix = /docs/personal# here, 'c' becomes '/' ># Mac = :docs

Re: RFC 100 (v1) Embed full URI support into Perl

2000-08-15 Thread Chaim Frenkel
You're still showing non-portable examples. What is the win? And what does "file://z/docs/personal" become? Or for that matter "file://u/frankeh/Projects" become? (I happen to live at a mount point /u. You are squeezing a little too hard here. There are seperate problems to be solved, whether

Re: RFC 100 (v1) Embed full URI support into Perl

2000-08-15 Thread Sam Tregar
On Tue, 15 Aug 2000, Nathan Wiger wrote: > With URI support, you still have to contort a little, but not as much. > Here's some better examples from an email I sent earlier: > >$fo = open "file://c/docs/personal"; > ># Unix = /docs/personal# here, 'c' becomes '/' ># Mac = :docs

Re: RFC 100 (v1) Embed full URI support into Perl

2000-08-15 Thread Nathan Wiger
Sam Tregar wrote: > > How is this better than File::Spec's approach? File::Spec has the idea and representation dead on. However, the interface is a pain; to write portable scripts you have to go through some contortions. With URI support, you still have to contort a little, but not as much. Her

Re: RFC 100 (v1) Embed full URI support into Perl

2000-08-15 Thread Sam Tregar
On 14 Aug 2000, Perl6 RFC Librarian wrote: >$fo = open "C:\Windows\System";# non-portable >$fo = open "file://C|/Windows/System"; # portable Can you explain how the second is portable to non-Windows systems? What does "C|" mean on my Linux box? >unlink "/local/etc/script.co

Re: RFC 100 (v1) Embed full URI support into Perl

2000-08-15 Thread Nathan Wiger
Chaim Frenkel wrote: > > > "PRL" == Perl6 RFC Librarian <[EMAIL PROTECTED]> writes: > > PRL>$fo = open "C:\Windows\System";# non-portable > PRL>$fo = open "file://C|/Windows/System"; # portable > > In what way is the second example portable? I don't think it will > do anythi

Re: RFC 100 (v1) Embed full URI support into Perl

2000-08-14 Thread Chaim Frenkel
> "PRL" == Perl6 RFC Librarian <[EMAIL PROTECTED]> writes: PRL>$fo = open "C:\Windows\System";# non-portable PRL>$fo = open "file://C|/Windows/System"; # portable In what way is the second example portable? I don't think it will do anything useful on any of my *nix boxes. PR

RFC 100 (v1) Embed full URI support into Perl

2000-08-14 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Embed full URI support into Perl =head1 VERSION Maintainer: Nathan Wiger <[EMAIL PROTECTED]> Date: 14 Aug 2000 Version: 1 Mailing List: [EMAIL PROTECTED] Number: 100 Status: Developing =h