>> No, sorry to be unclear. The get_* methods have to respect the order in
>> which data was placed into the buffer by the put_* methods. So, for example,
>> this is true:
>
> But what happens if I call the functions out of order?
Then you get incorrect data. Which is, perhaps, not the best way
[Quoting Benjamin Trott, on March 14 2001, 10:31, in "Re: Repost: Namespac"]
> How about Data::Buffer?
Better.
> No, sorry to be unclear. The get_* methods have to respect the order in
> which data was placed into the buffer by the put_* methods. So, for example,
> this is true:
But what happe
> Somehow this doesn't look IO related to me.
Yes, you're perhaps right.
How about Data::Buffer? Any other suggestions?
>> All of the I and I methods respect the
>> internal offset state in the buffer object. This means
>> that, for example, if you call I twice in a
>> row, you can be ensured t
[Quoting Benjamin Trott, on March 12 2001, 13:03, in "Repost: Namespace re"]
> use IO::Buffer;
> my $buffer = IO::Buffer->new;
>
> ## Add a 32-bit integer.
> $buffer->put_int32(10932930);
>
> ## Get it back.
> my $int = $buffer->get_int32;
Somehow this doesn't look IO r
--
I'm re-sending this as I thought it may have been overlooked the first time
I sent it, on March 1, 2001. This is a registration request for my module
IO::Buffer.
--
My CPAN ID is BTROTT. I'd like to contribute the following module to CPAN:
Name DSLI Description
Hi--
My CPAN ID is BTROTT. I'd like to contribute the following module to CPAN:
Name DSLI Description Info
---
IO::Buffer bdp0 Read/write string buffering class. BTROTT
IO::Buffer is used within
