On Tue, Sep 10, 2002 at 07:26:58PM +0200, Peter Gibbs wrote:
> Graham Barr wrote:
>
> > As well as supporting big/little endian specifically, should we support
> "native"
> > ie packed in the same endian as the machine the code is being run on.
>
> Certainly. I think we would want also want nati
Graham Barr wrote:
> As well as supporting big/little endian specifically, should we support
"native"
> ie packed in the same endian as the machine the code is being run on.
Certainly. I think we would want also want native sizes, so we can
ask for short, int, long etc and get the platform's siz
On Tue, Sep 10, 2002 at 06:01:23PM +0200, Peter Gibbs wrote:
> Attached is a sample implementation of a minor subset of
> pack/unpack functionality. Code is not optimised in any way,
> and error checking is basically non-existent.
>
> Opcodes are:
> convert Sx, Iy, Iz - pack integer Iy into
On Tue, 2002-09-10 at 12:01, Peter Gibbs wrote:
> Attached is a sample implementation of a minor subset of
> pack/unpack functionality. Code is not optimised in any way,
> and error checking is basically non-existent.
>
> Opcodes are:
> convert Sx, Iy, Iz - pack integer Iy into string Sx pe
Attached is a sample implementation of a minor subset of
pack/unpack functionality. Code is not optimised in any way,
and error checking is basically non-existent.
Opcodes are:
convert Sx, Iy, Iz - pack integer Iy into string Sx per type Iz
convert Ix, Sy, Iz - unpack integer Ix from
On Mon, 2002-09-09 at 21:42, Clinton A. Pierce wrote:
> >Should these conversions be individual instructions (e.g. "uint2string")
> >or should there be a single-target "pack" analog in the PBC?
>
> I like the idea of having a single pack/unpack instruction, with some kind
> of argument mechanis
At 03:01 PM 9/9/2002 -0400, Aaron Sherman wrote:
>I'd like to start a dialog
And since this thread is quiet, I'll throw some uneducated opinions on it
to help it along.
>about the P[arrot|erl] interface on the
>matter of converting low-level types. ord and chr are Perl functions for
>doing two
I'd like to start a dialog about the P[arrot|erl] interface on the
matter of converting low-level types. ord and chr are Perl functions for
doing two very specialized conversions, but I'm thinking Parrot needs to
provide a general-purpose number/[bit]?string conversion ala Perl's
pack/unpack so t
