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

[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: RFC 14 (v2) Modify open() to support FileObjects and

[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) indistinguishable from native
in the UNIX case at least.

-- 
Nick Ing-Simmons

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

[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 the single-arg form of select() is the
one you're suggesting for deprecation, and not the four-arg form.

The 4 arg form will be deprecated somewhere else. Splitting the function 
is a good idea...

-- 
Nick Ing-Simmons

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

[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? (I happen to
 live at a mount point /u.

You're missing an / under the example I showed. And extra / would
specify root explicitly.

But we're getting too tied up into details on this already. It's only
one of many many suggestions for portably dealing with filenames.

URI support has many advantages in its own right. For one thing, It
allows this:

   $fo = open "+ http://www.yahoo.com/";
   print $fo $query_string;
   $result = $fo;

To:

   1. automatically fork http-open
   2. create a POST on yahoo.com
   3. read the results back from the POST

 Have you ever used LWP?  It's already "really cool".  Should we package it
 with Perl6?  Sure!  Should we try to cram its many protocols into open?
 I'm not so sure.

Please read RFC's 14 and 101. Nothing is getting crammed into open.
Rather, open() is providing a portable mechanism for new file types and
methods to be easily accessed. Please read the RFC, it will help clear
this up. If you want to wait, v4 should be out tomorrow, which should be
even better.

-Nate

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

[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