[ragel-users] Debugging colm for win32.

William Ahern william at 25thandClement.com
Tue Apr 1 18:11:47 UTC 2014

On Tue, Apr 01, 2014 at 01:00:15PM -0400, Bob Paddock wrote:
> > For win64,
> > fairly extensive changes would be needed since colm assumes pointers = long
> > data type, but in windows pointers = long long.
> I've not looked at the code in question, so don't know if this helps.
> Pointers should not be long nor long long they should be size_t .
> See <stddef.h> and <stdint.h>.
> When we move to 128 bit parts we'd have to go down this road again,
> that is what size_t is meant to prevent.  It is the difference between
> memory space and arithmetic bit widths.

This isn't true in C. In C the only well-defined way to convert a pointer to
an integer and back again is via intptr_t or uintptr_t.

Does C++ really require the same behavior for size_t?

ragel-users mailing list
ragel-users at complang.org

More information about the ragel-users mailing list