On Wednesday 06 February 2002 04:53, Simon Glover wrote:
> 1. What should we do if the array contains strings of more than one type
> and/or encoding? Clearly we need to do some kind of transcoding, but how
> do we decide what to transcode to? I've had a look in strings.pod but it
> doesn't se
On Mon, 4 Feb 2002, Alex Gough wrote:
> On Mon, 4 Feb 2002, Simon Glover wrote:
>
> > Re the former, am I right in thinking that assignment from a PerlArray
> > to a non-PMC register should always be in scalar context; ie that:
> >
> > new P0, PerlArray
> > set S0, P0
> >
> > shou
On Mon, 4 Feb 2002, Simon Glover wrote:
> Re the former, am I right in thinking that assignment from a PerlArray
> to a non-PMC register should always be in scalar context; ie that:
>
> new P0, PerlArray
> set S0, P0
>
> should lead to S0 having the value "0" and not ""?
"string" is
OK, I've revised the tests for C in line with Alex's
concerns, and added explicit tests for PerlInts and PerlNums. As yet
there are still no PerlArray or PerlHash tests.
Re the former, am I right in thinking that assignment from a PerlArray
to a non-PMC register should always be in scalar
On Fri, 1 Feb 2002, Alex Gough wrote:
> On Fri, 1 Feb 2002, Simon Glover wrote:
>
> > The enclosed patch implements the last of these, and adds tests for
> > PerlUndefs and PerlStrings (and implicitly PerlInts and PerlNums -
> > should we also add explicit tests for these?). I haven't adde
On Fri, 1 Feb 2002, Simon Glover wrote:
>
> There are a number of set ops documented in core.ops that haven't
> actually been implemented - conversion from STR to INT/NUM (and
> vice versa), plus conversion from PMCs to STR.
>
> The enclosed patch implements the last of these, and adds tests
There are a number of set ops documented in core.ops that haven't
actually been implemented - conversion from STR to INT/NUM (and
vice versa), plus conversion from PMCs to STR.
The enclosed patch implements the last of these, and adds tests for
PerlUndefs and PerlStrings (and implicitly
