Re: union type is evil, redux

Look, what Ben is saying AFAICT is that where currently we do

Lisp_Object foo (Lisp_Object); Lisp_Object bar (Lisp_object x) { Lisp_Object y; y = foo(x); return y; } etc all over the place, it works correctly. That is, with typedef int Lisp_Object; it fails _intermittently_ with the union type. In order to make the union type work, probably we'd have to do something like #define a LISP_ASSIGN macro in order to enforce explicit temporaries and replace all object assignments with macro calls Lisp_object bar (Lisp_Object x) { Lisp_Object y; LISP_ASSIGN(y,x); return y; } This is _not_ a win. And replacing just the "dangerous ones" is GCPRO all over again.