Re: XEmacs at a crossroads

ht writes:

> Great, thank you!  [disabling ASLR] moves me on a step, definitely.
> More details later in the week, I hope.

I can now compile and run an x86_64 xemacs using Visual Studio 2015.

_But_, there are over 2192 warnings (1880 _distinct_) about possible
data loss stemming from differences in size.  Most of these arise from
the disconnect between the sizes of int, long, and EMACS_INT/VOID_P/and
friends:

                                int long EMACS_INT
 Cygwin/gcc     64-bit:          4   8      8
 Windows/VS2015 64-bit:          4   4      8

It seems . . . unlikely that _all_ of these warnings are harmless, so
short of slowly working through all of the cases I don't see that it's
plausible to make a release described as fully 64-bit-compatible.

Sigh.

Not sure about mingw, i.e. what ? is in a further row to the above
table:

 Windows/x86_64-w64-mingw32-gcc  4   ?      8

Anybody besides me care about this?

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: [email protected]
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]