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 14 (v4) Modify open() to support FileObjects and Extensibility

2000-09-17 Thread Michael G Schwern
On Sun, Sep 17, 2000 at 07:16:16PM -0700, Nathan Wiger wrote: > Well, as Tom pointed out to me this already exists in 5.6 as part of > FileHandle: I never liked FileHandle. ;) It appears to have gone into IO::Handle in 5.003_07! Wow. Okay, given that its such a venerable feature and the world i

Re: RFC 30 (v4) STDIN, STDOUT, STDERR, ARGV, and DATA should become scalars

2000-09-17 Thread Nathan Wiger
Tom Christiansen wrote: > > >Scalars hold references to objects. Filehandles should, ultimately, > >be objects, as should directory handles. > > I haven't yet seen anybody yet propose bifurcating {file,directory}handles. > This would certainly be nice. If I'm understanding what you mean, I bel

Re: RFC 30 (v4) STDIN, STDOUT, STDERR, ARGV, and DATA should become scalars

2000-09-17 Thread Tom Christiansen
>This is already allowed. It's called "passing in a bareword". >And barewords are just strings. Are you proposing >that "a bareword should now mean a filehandle", so that > copydata(STDIN, STDOUT); >means something different from > copydata('STDIN', 'STDOUT'); >or > cop

Re: RFC 30 (v4) STDIN, STDOUT, STDERR, ARGV, and DATA should become scalars

2000-09-17 Thread Tom Christiansen
>> What if it's an anonymous stream? >How do you open an anonymous stream? Me? This way: local(*HITHER, *THITHER); pipe(HITHER, THITHER) .. or, I suppose, my($hither, $thither); pipe($hither, $thither) .. or even pipe(my $hither, $thither) .. Why, how d

Re: RFC 14 (v4) Modify open() to support FileObjects and Extensibility

2000-09-17 Thread Nathan Wiger
Michael G Schwern wrote: > > On Sun, Sep 17, 2000 at 05:35:47AM -, Perl6 RFC Librarian wrote: > >$fo->untaint - Removes tainting from that data source > > I can guarantee this will be abused and severely water down the > utility of taint mode. Well, as Tom pointed out to me this alre

Re: RFC 30 (v4) STDIN, STDOUT, STDERR, ARGV, and DATA should become scalars

2000-09-17 Thread Tom Christiansen
>So why not allow undecorated variables a larger existence? We already have them. You can use a sub name or a package name where you mean an "undecorated variable". In fact, you can have things generate/populate new subs or packages as you like it. use Funny_Business; frob Funny "

Re: RFC 30 (v4) STDIN, STDOUT, STDERR, ARGV, and DATA should become scalars

2000-09-17 Thread Tom Christiansen
> * Have to use ugly globref syntax to pass them around reliably. No, you don't. You can use globs. But only if you don't have prototypes, like sub opt(*). > * Not first-class objects, so you can't subclass them. That's not a good argument. I can't subclass a number, either, nor

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

Re: RFC 14 (v4) Modify open() to support FileObjects and Extensibility

2000-09-17 Thread Michael G Schwern
On Sun, Sep 17, 2000 at 05:35:47AM -, Perl6 RFC Librarian wrote: >$fo->untaint - Removes tainting from that data source I can guarantee this will be abused and severely water down the utility of taint mode. A discussion of easy untainting came up on perl6-internals and fairly universa