🚀 go-pugleaf

>(I've often wondered exactly what C
>ended up looking like on that machine, as pointers and ints are definitely not
>the same, and casting an int to a pointer makes no sense).

I suspect it looks like a C that punishes people who think pointers are
the same as "int"s; I wish there were *more* C implementations like
that, in order to break some C programmers' bad habits.  I've heard a
claim that pointers are 128 bits long; that may have been done so that
pointers to elements of arrays contain, in effect, the bounds of the
array, so that pointer arithmetic on those pointers can be checked to
make sure it results in a pointer that points into the same array as the
original pointer.

(And yes, such a C implementation *can* be a valid ANSI C
implementation, even though it doesn't allow the kind of fast-and-loose
glop that some C programmers think is key to the C language....)