> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
DS> It works pretty well, all things considered. Not the easiest way to
DS> program, but async code's always a big pain in the neck.
ahh, back to the days of rt-11 which had optional callbacks for all of
its i/o calls including files. n
At 07:11 PM 1/5/01 +, [EMAIL PROTECTED] wrote:
>Nicholas Clark <[EMAIL PROTECTED]> writes:
> >> and maybe have the return data have some 'I/O complete' marker so
> async I/O
> >> will work out properly.
>
>Anyone that has experience in writing prefetch style code please weigh in
>with the pit
Nicholas Clark <[EMAIL PROTECTED]> writes:
>
>tell can be seek F, 0, SEEK_CUR
I initally had stdio like split seek/tell. I actually implemented
the merged form as you suggest - but it turned out to be a mistake
so they are currently separate again.
The reason it is a mistake is one wants seek(F
> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
DS> I've been pretty much assuming we'd need:
DS>open
DS>close
DS>seek
DS>tell
DS>push_filter
DS>pop_filter
DS>read
DS>unread
DS>write
DS>prefetch
DS> and maybe have the return
> "FB" == Filipe Brandenburger <[EMAIL PROTECTED]> writes:
FB> What about pread and pwrite, for reading and writing to seekable files
FB> in multiple threads? pread and pwrite get as a parameter a offset that
FB> they use to seek the file before reading or writing, but doing it
>On Fri, Jan 05, 2001 at 12:37:39PM -0500, Dan Sugalski wrote:
>> I've been pretty much assuming we'd need:
>>
>>open
>>close
>>seek
>>tell
>>push_filter
>>pop_filter
>>read
>>unread
>>write
>>prefetch
>>
What abo
On Fri, Jan 05, 2001 at 12:37:39PM -0500, Dan Sugalski wrote:
> I've been pretty much assuming we'd need:
>
>open
>close
>seek
>tell
tell can be seek F, 0, SEEK_CUR
(unless tell is intended to return some other information on unseekable
files. In which case internally one could
At 09:22 PM 1/4/01 +, [EMAIL PROTECTED] wrote:
>Simon Cozens <[EMAIL PROTECTED]> writes:
> >On Wed, Jan 03, 2001 at 11:03:08PM +, Nick Ing-Simmons wrote:
> >> I am willing to cast bleadperl5's PerlIO into the form of a _draft_ PDD
> >> for perl6 - i.e. "this is what it does now", not "this
Simon Cozens <[EMAIL PROTECTED]> writes:
>On Wed, Jan 03, 2001 at 11:03:08PM +, Nick Ing-Simmons wrote:
>> I am willing to cast bleadperl5's PerlIO into the form of a _draft_ PDD
>> for perl6 - i.e. "this is what it does now", not "this is what it should do".
>
>I have a feeling the two are go
At 12:50 PM 1/4/01 +, Simon Cozens wrote:
>On Wed, Jan 03, 2001 at 11:03:08PM +, Nick Ing-Simmons wrote:
> > I am willing to cast bleadperl5's PerlIO into the form of a _draft_ PDD
> > for perl6 - i.e. "this is what it does now", not "this is what it
> should do".
>
>I have a feeling the
On Wed, Jan 03, 2001 at 11:03:08PM +, Nick Ing-Simmons wrote:
> I am willing to cast bleadperl5's PerlIO into the form of a _draft_ PDD
> for perl6 - i.e. "this is what it does now", not "this is what it should do".
I have a feeling the two are going to be very similar.
--
"A word to the wi
> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
DS> At 11:03 PM 1/3/01 +, Nick Ing-Simmons wrote:
>> Dan Sugalski <[EMAIL PROTECTED]> writes:
>> >Would someone like to take a crack at a PDD for the PerlIO system? It
>> >doesn't need to be particularly fancy (nor complete) to st
At 11:03 PM 1/3/01 +, Nick Ing-Simmons wrote:
>Dan Sugalski <[EMAIL PROTECTED]> writes:
> >Would someone like to take a crack at a PDD for the PerlIO system? It
> >doesn't need to be particularly fancy (nor complete) to start with, but
> >having one will give us a place to work from. (Waiting
> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
DS> Would someone like to take a crack at a PDD for the PerlIO system?
DS> It doesn't need to be particularly fancy (nor complete) to start
DS> with, but having one will give us a place to work from. (Waiting
DS> for me to spec it out
Dan Sugalski <[EMAIL PROTECTED]> writes:
>Would someone like to take a crack at a PDD for the PerlIO system? It
>doesn't need to be particularly fancy (nor complete) to start with, but
>having one will give us a place to work from. (Waiting for me to spec it
>out may take a while...)
I am will
Would someone like to take a crack at a PDD for the PerlIO system? It
doesn't need to be particularly fancy (nor complete) to start with, but
having one will give us a place to work from. (Waiting for me to spec it
out may take a while...)
Dan
-
16 matches
Mail list logo
