Re: [Devel] 16, 32, and 64 bit ints [was: Patch needed to compile freetype-2.0.1 on Windows XP64 Beta 1]

[Werner LEMBERG]

> One of my points is that I wanted to look at the casts (I failed to
> mention this the first time).  Casts are fine, but the more we can
> avoid them, the better.  I want to investigate how we can use a 32
> bit int as FT_Long on a 64 bit box and avoid some of the issues we
> have seen, etc...  That is, for those things we know are supposed to
> be 32 bits wide, use int32_t, or some such.  This would go a long
> way torwards getting rid of unnecessary casts and make the code more
> robust for 64 bit and 16 bit platforms, etc...

Since we don't use size_t and friends in FreeType (David, any reason
for this?), casts are unavoidable if pointer arithmetic is involved.
Henrik did a good job by using the proper types (which I have checked).

IMHO a cast is better than no cast in such situations -- for future
cleanups, it gives a hint where to do something.


    Werner