On Monday 01 October 2001 08:36 am, Simon Cozens wrote:
> On Mon, Oct 01, 2001 at 07:20:56AM -0500, Gibbs Tanton - tgibbs wrote:
> > Casting to IV doesn't actually hurt anything (unless there is an
> > alignment issue); however, casting to char* is the more idiomatic way of
> > doing it. I'll comm
On Monday 01 October 2001 08:20 am, Gibbs Tanton - tgibbs wrote:
> Casting to IV doesn't actually hurt anything (unless there is an alignment
> issue); however, casting to char* is the more idiomatic way of doing it.
> I'll commit this unless Simon says he is going to handle it in "The Great
> Ren
Yeah, I knew we were trying to stay away from char*; however, since this is
in the native string library, there's pretty much no getting around it :)
-Original Message-
From: Simon Cozens
To: '[EMAIL PROTECTED] '
Sent: 10/1/2001 7:36 AM
Subject: Re: [PATCH] Bad cast
On Mon, Oct 01, 2001 at 07:20:56AM -0500, Gibbs Tanton - tgibbs wrote:
> Casting to IV doesn't actually hurt anything (unless there is an alignment
> issue); however, casting to char* is the more idiomatic way of doing it.
> I'll commit this unless Simon says he is going to handle it in "The Great
Bryan C. Warnock
To: [EMAIL PROTECTED]
Sent: 9/30/2001 10:31 PM
Subject: [PATCH] Bad cast
Casting to IV is not the way to do this.
Index: strnative.c
===
RCS file: /home/perlcvs/parrot/strnative.c,v
retrieving revision 1.12
diff -
Casting to IV is not the way to do this.
Index: strnative.c
===
RCS file: /home/perlcvs/parrot/strnative.c,v
retrieving revision 1.12
diff -c -r1.12 strnative.c
*** strnative.c 2001/09/18 13:42:41 1.12
--- strnative.c 2001/10/01
