Re: RFC 39 (v2) Perl should have a print operator

2000-08-16 Thread Nathan Wiger
> >"Print this line.\n"<; Some questions: 1. How do you specify alternate filehandles to output to? select() doesn't count for the purposes of this question. 2. How do you support the list form of print, namely: print "Hello there ", $r->fullname, "!\n"; 3. Can you

RFC 39 (v2) Perl should have a print operator

2000-08-16 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Perl should have a print operator =head1 VERSION Maintainer: Jon Ericson <[EMAIL PROTECTED]> Date: 5 August 2000 Last-Modified: 17 August 2000 Version: 2 Mailing List: [EMAIL PROTECTED] Number:

RFC 34 (v2) Angle brackets should not be used for file globbing

2000-08-16 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Angle brackets should not be used for file globbing =head1 VERSION Maintainer: Jon Ericson <[EMAIL PROTECTED]> Date: 4 August 2000 Last-Modified: 17 August 2000 Version: 2 Mailing List: [EMAIL PRO

Re: RFC 30 (v2) STDIN, STDOUT, and STDERR should be renamed

2000-08-16 Thread Nathan Wiger
Graham Barr wrote: > > > Create a new handle, like $DEFOUT. Then there would be no need > for selectsaver either as you would do the equiv. of > > local($DEFOUT) = $newhandle; Just submitted an RFC on this exact idea. -Nate

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 30 (v2) STDIN, STDOUT, and STDERR should be renamed

2000-08-16 Thread Graham Barr
On Wed, Aug 16, 2000 at 08:27:04PM +, Nick Ing-Simmons wrote: > Perl6 Rfc Librarian <[EMAIL PROTECTED]> writes: > > > >In addition, this RFC recommends deprecating select(), since it is no > >longer needed with the new fileobject approach described in RFC 14. > > > > > > $oldoutput = select(

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

2000-08-16 Thread Tim Jenness
On Tue, 15 Aug 2000, Nathan Wiger wrote: > Chaim Frenkel wrote: > > > > You forget that open() handles all the magic. "| ...", " ...|", and > > the rest of the family. Sysopen specifically doesn't. So one could > > easily (and does) use open to do the magic, and then uses sysread/syswrite > > to

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

2000-08-16 Thread Nathan Wiger
Chaim Frenkel wrote: > > You forget that open() handles all the magic. "| ...", " ...|", and > the rest of the family. Sysopen specifically doesn't. So one could > easily (and does) use open to do the magic, and then uses sysread/syswrite > to handle the dirty details of playing with a pipe. Yea

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

2000-08-16 Thread Nathan Wiger
> Random thoughts: > > open "http://www.perl.com"; > open "http://www.perl.com?foo=bar&baz=blat"; > open "http://www.perl.com", %args; > open "http://www.perl.com", { mode => 'POST' }, %args; > > Hmm. I think that "modes" should be made explicit rather than relyi

Re: RFC 30 (v2) STDIN, STDOUT, and STDERR should be renamed

2000-08-16 Thread Nick Ing-Simmons
Nathan Wiger <[EMAIL PROTECTED]> writes: > >For other stuff, like print(), instead of using the "currently selected >filehandle", just always have it print to $STDOUT unless something's >specified. So: > > $oldstdout = $STDOUT; > $STDOUT = $myfileobject; > print "Hello, world!"; # always p

Re: RFC 30 (v2) STDIN, STDOUT, and STDERR should be renamed

2000-08-16 Thread Nick Ing-Simmons
Michael Fowler <[EMAIL PROTECTED]> writes: >On Sat, Aug 12, 2000 at 08:49:00AM -, Perl6 RFC Librarian wrote: >> In addition, this RFC recommends deprecating select(), since it is no >> longer needed with the new fileobject approach described in RFC 14. > >You should probably mention here that

Re: RFC 30 (v2) STDIN, STDOUT, and STDERR should be renamed

2000-08-16 Thread Nick Ing-Simmons
Perl6 Rfc Librarian <[EMAIL PROTECTED]> writes: > >In addition, this RFC recommends deprecating select(), since it is no >longer needed with the new fileobject approach described in RFC 14. > > > $oldoutput = select($newoutput); > >Can now be written simply as reassignments: > > $oldoutput = $

Re: Internal Filename Representations (was Re: Summary of I/O related RFCs)

2000-08-16 Thread Nick Ing-Simmons
Johan Vromans <[EMAIL PROTECTED]> writes: >Nathan Wiger <[EMAIL PROTECTED]> writes: > >>$fo = open "C:\Windows\System\IOSUBSYS\RMM.PDR"; >>$fo->pathdrive = "C:" ; > >I think the drive is "C", not "C:". The reason for including the ':' is so that the rule for reconstructing the path is ea

Re: Internal Filename Representations (was Re: Summary of I/O related RFCs)

2000-08-16 Thread Nick Ing-Simmons
Jarkko Hietaniemi <[EMAIL PROTECTED]> writes: >On Fri, Aug 11, 2000 at 02:16:31AM -0700, Nathan Wiger wrote: >> [cc'ed on internals as FYI] >> >> > =item 36 (v1): Structured Internal Representation of Filenames >> >> I think this should be discussed a good amount. I think URIs are cool, >> but t

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

2000-08-16 Thread Nick Ing-Simmons
Nathan Wiger <[EMAIL PROTECTED]> writes: >Admittedly, it does look cooler, but consider this: > > open 'http://www.yahoo.com/'; > open 'https://www.etrade.com/';# what module? https? Yes - if you don't have one it fails "https protocol not found". > >No matter what, you're going to h

Re: RFC 69 (v2) Standardize input record separator (for

2000-08-16 Thread Nick Ing-Simmons
Simply Hao <[EMAIL PROTECTED]> writes: >> But there is no way that I want under, any circumstance, _all_ >> line endings active at the same time. > >Why not? Because native tools won't behave like that and we want to mimic them (at least as an option). > >Well, how about this proposal then? > >D

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

2000-08-16 Thread Nick Ing-Simmons
Chaim Frenkel <[EMAIL PROTECTED]> writes: >What about native extensions? I think VMS (and the old TOPS10) had versions >as part of the file name. > >Do URIs have this capablity? > >And what does a read of a directory return? URIs or Native? Relative URIs I assume - what are (hopefully) indistingu

Re: Line disciplines (was Re: RFC 69 (v3) Standardize input recordseparator)

2000-08-16 Thread Dave Storrs
On Wed, 16 Aug 2000, Jonathan Scott Duff wrote: > On Wed, Aug 16, 2000 at 07:39:33AM -0700, Dave Storrs wrote: > > How about instead we build the DFA [regex engine], with its more > > limited syntax, but it must be manually turned on by use of a flag > > (similar to the 'o' precompiled fla

Re: Line disciplines (was Re: RFC 69 (v3) Standardize input record separator)

2000-08-16 Thread Simply Hao
I'll try to scrap and rewrite the RFC this weekend. > $/ = qr/[\r\n]/f; # fast ? How about we use the specialized DFA regex, but also slightly different notation? -Hao

Re: Line disciplines (was Re: RFC 69 (v3) Standardize input record separator)

2000-08-16 Thread Jonathan Scott Duff
On Wed, Aug 16, 2000 at 07:39:33AM -0700, Dave Storrs wrote: > The idea of having two different regex "languages" in Perl makes > me very, very nervous. Potential for confusion Indeed. > How about instead we build the DFA as you describe, with its more > limited syntax, but it must

Re: Line disciplines (was Re: RFC 69 (v3) Standardize input recordseparator)

2000-08-16 Thread Dave Storrs
On Sat, 12 Aug 2000, Bart Lateur wrote: [...] > different either. I too think that the input file separator should have > regexish features, if the programmer wishes so. Now, one can only set $/ [...] > My thoughts would be: a DFA regex engine, i.e. a state machine which is > controlled by the n

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