On Monday 31 December 2001 11:57 pm, Boris Tschirschwitz wrote:
> I really don't see what UINTVALS are good for.
Here are reflections on my stance
http:[EMAIL PROTECTED]/msg06913.html
> I wonder if making the interpreter so much bigger (with all the
> unsigned counterparts of int arithmetic
I really don't see what UINTVALS are good for.
I wonder if making the interpreter so much bigger (with all the
unsigned counterparts of int arithmetic functions) just for being able to
use native ints instead of bigints a little longer (*2) wouldn't cost more
than it gains.
If it is for type check
On Monday 31 December 2001 11:14 pm, David & Lisa Jacobs wrote:
{patch}
This patch merges changes I made in the same areas.
Index: encodings/singlebyte.c
===
RCS file: /home/perlcvs/parrot/encodings/singlebyte.c,v
retrieving revisi
I have a LOT of changes I want to make with respect to unsigned ints. The
net result will be fewer warnings along with lower chance of errors. To
keep from getting out of sync with everyone I'm going to break it into as
small pieces as I can. Unfortunately, this made lead to a few extra
warning
