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

2000-09-19 Thread Piers Cawley
Chaim Frenkel <[EMAIL PROTECTED]> writes: > > "NC" == Nicholas Clark <[EMAIL PROTECTED]> writes: > > NC> $htdoc = open uri "http://www.yahoo.com" or die; with uri in the > NC> standard library and also make it easy to stack the module that > NC> does uri at the top of 'file' so that the defa

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

2000-09-18 Thread Chaim Frenkel
> "NC" == Nicholas Clark <[EMAIL PROTECTED]> writes: NC> $htdoc = open uri "http://www.yahoo.com" or die; NC> with uri in the standard library NC> and also make it easy to stack the module that does uri at the top of 'file' NC> so that the default is to call the uri stuff. Is it just me, but

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

2000-09-18 Thread Nicholas Clark
On Mon, Sep 18, 2000 at 08:26:26AM -0700, Nathan Wiger wrote: > Hildo Biersma wrote: > > > > > Personally I hated it. And I distinctly remember saying so. And I > > > still hate it. > > > > I dislike it too. URIs are a user-space matter and should not be > > built-in to the language - put it in

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

2000-09-18 Thread Nathan Wiger
Hildo Biersma wrote: > > > Personally I hated it. And I distinctly remember saying so. And I > > still hate it. > > I dislike it too. URIs are a user-space matter and should not be > built-in to the language - put it in a module. And if you have an OS > that implements URIs directly, well then

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

2000-09-18 Thread Piers Cawley
Hildo Biersma <[EMAIL PROTECTED]> writes: > > > =head1 NOTES ON FREEZE > > > > > > The only comments received were on my crappy examples, which have been > > > clarified. Everyone seemed to like the idea. > > > > Personally I hated it. And I distinctly remember saying so. And I > > still hate it

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

2000-09-18 Thread Hildo Biersma
> > =head1 NOTES ON FREEZE > > > > The only comments received were on my crappy examples, which have been > > clarified. Everyone seemed to like the idea. > > Personally I hated it. And I distinctly remember saying so. And I > still hate it. I dislike it too. URIs are a user-space matter and sh

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

2000-09-18 Thread Piers Cawley
Perl6 RFC Librarian <[EMAIL PROTECTED]> writes: > 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 > Last-Modified: 1

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

2000-09-17 Thread Nathan Wiger
> I'd rather see you drop (or footnote) the discussion of how the various > systems are going to map content among themselves, and focus more on > what the construct allows. For instance, returning to some of the > original implementation ideas, that the location information be passed > to the pr

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

2000-09-17 Thread Bryan C . Warnock
On Sun, 17 Sep 2000, Nathan Wiger wrote: > > The only comments received were on my crappy examples, which have been > clarified. Well, sort of. More comments on "crappy" examples. :-) > > The key syntax benefit is #1. This lets us use URIs in any function to > allow scripts that can be used

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

2000-09-17 Thread Michael G Schwern
On Sun, Sep 17, 2000 at 05:36:56AM -, Perl6 RFC Librarian wrote: >unlink "/local/etc/script.conf";# non-portable >unlink "file:///local/etc/script.conf"; # portable '/local/etc/script.conf' is very unlikely to exist or be a sensible filename on Windows or MacOS (or Unix. Shou

RFC 100 (v2) Embed full URI support into Perl

2000-09-16 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 Last-Modified: 16 Sep 2000 Mailing List: [EMAIL PROTECTED] Number: 100 Version: 2