Re: PerlIO - what next? - (should getc get a character?)

[Nick Ing-Simmons]

Uri Guttman [EMAIL PROTECTED] writes:
 "NI" == Nick Ing-Simmons [EMAIL PROTECTED] writes:

p5p removed

  NI I have guts of a stack-of-layers PerlIO scheme coded now 
  NI (//depot/perlio/... for those with perforce access - merge to 5.7.0
  NI will occur as soon a Jarrko likes.)

does it support multiple instances for threads 

Not yet.

and async i/o? 

If I can find a system that has async IO I will give it a try.
I may do Win32 system that way ...

what about
event handling and such? 

What I have so far is "sfio like" except that the "vtable" that disciplines
define (which I call layers) is larger and it is coded in a more object-oriented
style (and of course is under perl's license).

There is nothing stopping an event system doing 

  splice(@perlio::layers,1,0,@layers_to_handle_blocking);

but the mechanism to mess with per-handle layer stack is not really there yet.
Right now we only have unix (read), stdio (fread) and perlio (buffer layer).
I/we need to code a few more "layers" to get a feel for 


i think we need to make a proper api spec on
how the i/o subsystem looks to the outside world and also how it
interacts with the perl6 kernel. as the kernel hasn't been spec'ed or
whatever, we have to wait on that some more.

but i am glad to hear of code that we can use as a first draft.

I am not sure this code is a "draft" for perl6 - more of an experiment 
so we can see what does('nt) work. The OO ANSI-C with vtable stuff I 
used is also and experiment to see what it costs before we start wholesale
coding of perl6.

-- 
Nick Ing-Simmons

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

[Nick Ing-Simmons]

Graham Barr [EMAIL PROTECTED] writes:
On Wed, Aug 09, 2000 at 11:41:42AM -0500, Jonathan Scott Duff wrote:
 How about this?
 
  open '/etc/passwd'; # file

OK

  open '/usr/local/bin/'; # directory (note the trailing '/')

Portability, not all platforms use /

Allowing URI/URL syntax can perhaps dodge the "portability" issue 
URLs use / so if user thinks URL they think /.

-- 
Nick Ing-Simmons