Re: 64-bit ints and non-capable hardware

2002-10-23 Thread Martin D Kealey
On Wed, 23 Oct 2002, Rhys Weatherley wrote: > Martin D Kealey wrote: > > [Frank Farance's paper] "specification based extended integer range" > > [at] http://wwwold.dkuug.dk/JTC1/SC22/WG14/docs/c9x/extended-integers/. > Very interesting proposal. I wish they had adopted it. Would > have saved me

Re: 64-bit ints and non-capable hardware

2002-10-22 Thread Rhys Weatherley
Martin D Kealey wrote: > I was wondering if anyone else followed the discussion in comp.std.c about > integer types, prior to the adoption of the C99 standard? There was a > substantial paper put out by Frank Farance, entitled "specification based > extended integer range" or SBEIR for short; see

Re: 64-bit ints and non-capable hardware

2002-10-22 Thread Dan Sugalski
At 6:25 PM -0400 10/21/02, Bryan C. Warnock wrote: On Mon, 2002-10-21 at 15:11, Dan Sugalski wrote: Okay, I'm about ready to just bite the bullet and declare that INTVALs have to be 64 bit integers. Which INTVALs? I registers. INTVAL, IMHAOSBRPO[1], is overused internally. I see little re

RE: 64-bit ints and non-capable hardware

2002-10-22 Thread Dan Sugalski
At 3:59 PM -0700 10/21/02, Brent Dax wrote: Dan Sugalski: # Okay, I'm about ready to just bite the bullet and declare that # INTVALs have to be 64 bit integers. # # Does anyone know of a platform that has neither native nor emulated # 64 bit integers? (One we're likely to run on, rather) Mac Clas

Re: 64-bit ints and non-capable hardware

2002-10-22 Thread Martin D Kealey
Dan Sugalski <[EMAIL PROTECTED]> wrote: > Okay, I'm about ready to just bite the bullet and declare that > INTVALs have to be 64 bit integers. > > Does anyone know of a platform that has neither native nor emulated > 64 bit integers? (One we're likely to run on, rather) I'm fairly new to Parrot

Re: 64-bit ints and non-capable hardware

2002-10-21 Thread Bryan C. Warnock
On Mon, 2002-10-21 at 15:11, Dan Sugalski wrote: > Okay, I'm about ready to just bite the bullet and declare that > INTVALs have to be 64 bit integers. Which INTVALs? INTVAL, IMHAOSBRPO[1], is overused internally. I see little relative performance and size damage if INTVAL is made 64 bits and re

RE: 64-bit ints and non-capable hardware

2002-10-21 Thread Brent Dax
Dan Sugalski: # Okay, I'm about ready to just bite the bullet and declare that # INTVALs have to be 64 bit integers. # # Does anyone know of a platform that has neither native nor emulated # 64 bit integers? (One we're likely to run on, rather) Mac Classic processors and Palm DragonBalls? By t

64-bit ints and non-capable hardware

2002-10-21 Thread Dan Sugalski
Okay, I'm about ready to just bite the bullet and declare that INTVALs have to be 64 bit integers. Does anyone know of a platform that has neither native nor emulated 64 bit integers? (One we're likely to run on, rather) -- Dan ---