On Thu, Sep 13, 2001 at 10:06:51AM +0100, Philip Kendall wrote: > I think we're also going to need an integer type which is guaranteed to be > the same width as a pointer, so we can freely typecast between the two. I thought that was what IVs are *for*. Simon
- Using int32_t instead of IV for code Hong Zhang
- Re: Using int32_t instead of IV for code Dan Sugalski
- Re: Using int32_t instead of IV for code Jarkko Hietaniemi
- Re: Using int32_t instead of IV for code Dan Sugalski
- Re: Using int32_t instead of IV for code Philip Kendall
- Re: Using int32_t instead of IV for code Simon Cozens
- Re: Using int32_t instead of IV for code Dan Sugalski
- Re: Using int32_t instead of IV for code Damien Neil
- Re: Using int32_t instead of IV for code Dan Sugalski
- Re: Using int32_t instead of IV for code Simon Cozens
- Re: Using int32_t instead of IV for code Andy Dougherty
- RE: Using int32_t instead of IV for code Hong Zhang
- Re: Using int32_t instead of IV for code Philip Kendall
- Re: Using int32_t instead of IV for code Andy Dougherty
- Re: Using int32_t instead of IV for code Dan Sugalski
- Re: Using int32_t instead of IV for code Buddha Buck