cuneiform team mailing list archive

[Jussi Pakkanen <jpakkane@xxxxxxxxx>]

On Fri, Feb 11, 2011 at 2:10 PM, Yury V. Zaytsev <yury@xxxxxxxxxx> wrote:

> The reason behind those is basically that the code makes implied
> assumptions on the type sizes which do not necessarily hold on various
> architectures, which in turn leads to invalid computations and memory
> corruption and as a result, although the program may compile, produces
> garbage output.

A quick note: stdint.h defines a type called intptr_t, which is an
integer large enough to hold a pointer in the current environment. So
it is int32 on x86, int64 on amd64 and so on. If you are passing
pointers around in integers, this is the type you should probably be
using.