RE: [PATCH] Re: Question about INTVAL vs. opcode_t sizes

2002-01-06 Thread Melvin Smith
At 06:30 PM 1/6/2002 -0800, Hong Zhang wrote: > > That's what I thought I remembered; in that case, here's a patch: > > > > Index: core.ops > > === > > RCS file: /home/perlcvs/parrot/core.ops,v > > retrieving revision 1.68 > > diff -u

RE: [PATCH] Re: Question about INTVAL vs. opcode_t sizes

2002-01-06 Thread Hong Zhang
> That's what I thought I remembered; in that case, here's a patch: > > Index: core.ops > === > RCS file: /home/perlcvs/parrot/core.ops,v > retrieving revision 1.68 > diff -u -r1.68 core.ops > --- core.ops 4 Jan 2002 02:36:25 -

Re: [PATCH] Re: Question about INTVAL vs. opcode_t sizes

2002-01-04 Thread Dan Sugalski
At 09:59 PM 1/4/2002 -0600, David M. Lloyd wrote: >That's what I thought I remembered; in that case, here's a patch: Applied, thanks. Dan --"it's like this"--- Dan Sugalski even

[PATCH] Re: Question about INTVAL vs. opcode_t sizes

2002-01-04 Thread David M. Lloyd
On Fri, 4 Jan 2002, Bryan C. Warnock wrote: > On Friday 04 January 2002 10:43 pm, David M. Lloyd wrote: > > > > So that you can use constants that are up to sizeof(opcode_t) bytes, but > > after that you're on your own. That raises a question, though: Do we > > want to move integer constants in

Re: Question about INTVAL vs. opcode_t sizes

2002-01-04 Thread Bryan C. Warnock
On Friday 04 January 2002 10:43 pm, David M. Lloyd wrote: > > So that you can use constants that are up to sizeof(opcode_t) bytes, but > after that you're on your own. That raises a question, though: Do we > want to move integer constants into the constant table? We're guaranteeing 32 bits of i