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 a module. And if you have an OS
> > that implements URIs directly, well then that module becomes really
> > simple :-)
>
> I'm not sure that URIs are a user-space matter. They're a widely
> accepted portable standard for spelling out resource locations. They
> also make this:
>
> $htdoc = open "http://www.yahoo.com" or die;
>
> Natively possible, without bloating the language. See RFC 14 for how
> this could work.
Should they go into the core?
Or should I register a URI handler to go
$htdoc = open uri "http://www.yahoo.com" or die;
with uri in the standard library
and also make it easy to stack the module that does uri at the top of 'file'
so that the default is to call the uri stuff.
This would keep the core smaller, but let any script that wants it get
"builtin" URIs with only one line.
RFC 14 is frozen, otherwise I'd suggest that the default handler isn't
'file' but 'magic' or 'perl' - ie something that knows about | for pipes,
& for dup'ing, |- for forking and soforth. 'file' could then be a vanilla
always-opens-a-file handler.
Nicholas Clark
