Re: [Emacs-diffs] trunk r117464: Shrink Lisp_Sub_Char_Table by preferring C integers to Lisp_Objects.

[Stefan Monnier]

>> So, I think it's unsafe to cast your new "struct Lisp_Sub_Char_Table"
>> to a "struct Lisp_Vector".  Maybe it does work on current existing
>> systems, but it's too fragile.
> I'll install verify() to catch future (broken) systems.

The problem is not only future systems.  On systems where Lisp_Object
are 64bit but can be aligned on a 32bit boundary (I expect this to be
the case for some 32bit systems --with-wide-int), if/when we optimize
the representation a bit more (i.e. merge `depth' and `min_char' into
a single 32bit word, by adding ":2" and ":30" after each field), your
code will probably fail.


        Stefan