Re: RFC 39 Perl should have a print operator

2000-09-05 Thread Eryq
ot;); I would really like to avoid adding more special operators when their functionality is not really primitive. -- ___ _ _ _ _ ___ _ / _ \| '_| | | |/ _ ' / Eryq (Erik Dorfman) | __/| | | |_| | |_| | President, ZeeGee Software Inc. \___||_| \__, |\__, |___/\ http://www.zeegee.com |___/|__/ [EMAIL PROTECTED]

Re: Cross-referencing RFC 186 with RFC 183 and RFC 79

2000-09-14 Thread Eryq
rint() then reduces to: sub CORE::print { $CORE::DEFOUT->print(@_); } Eryq

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

2000-09-14 Thread Eryq
ld references to objects. Filehandles should, ultimately, be objects, as should directory handles. Just my 10 centimes, Eryq

Re: Cross-referencing RFC 186 with RFC 183 and RFC 79

2000-09-14 Thread Eryq
a .t). All we'd need is one; it would be general-purpose, and you could just download it from CPAN and stick it into the t/ directory of any distribution. For more flexibility, the test could look at an inline_tests.t.list file in the cwd to determine *which* .pm's should be tested. Best of Both Worlds. :-) Eryq

Re: Cross-referencing RFC 186 with RFC 183 and RFC 79

2000-09-14 Thread Eryq
John Porter wrote: > > For more flexibility, the test could look at an inline_tests.t.list > > file in the cwd to determine *which* .pm's should be tested. > > This could be done now, without further ado. > > ## > # testing code here... > ... > ## > > Podulation

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

2000-09-14 Thread Eryq
"David L. Nicol" wrote: > > > >1. You must use globs to pass them in and out of functions > > This could be resolved by allowing undecorated types to be passed This is already allowed. It's called "passing in a bareword". And barewords are just strings. Are you proposing that "a barewor

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

2000-09-18 Thread Eryq
hat, then I'd love it if instances of X could automatically be used like this: my $x = new X; print $x "Hi there\n"; Anyway, I've said enough. Sorry if you've misconstrued it as my "calling your baby ugly". We love Perl, we truly do. We love it so much that we want it to be as easy as possible for others to learn, so that they can love it, too. > I haven't yet seen anybody yet propose bifurcating {file,directory}handles. > This would certainly be nice. You mean, like a handle with a built-in "tee" capability? Eryq