Re: HAVE_LONG_LONG_INT

Bruno wrote:
> I disagree. This would break the ability to compile with MSVC.  Last
> time I checked (Visual Studio 2015), it did not have 'long long',
> only __int64. Has this changed in Visual Studio 2017?

Are you sure? I don't have access to any version of MSVC right now,
but according to their own documentation[1], (unsigned) long long should
be there even in MSVC 2010?

But are we ever really using "long long"? A quick grep on all files in
the repo shows only a single usage of "long long" (actually "unsigned
long long"):

./src/spvw_sigsegv.d:29:  fprintf(stderr," %llu",(unsigned long
long)tm.gcfreed);

Other than that it's only typedefs (which could be changed to __int64
for MSVC) and code for the detection (whether there is long long
support or not).


[1] https://msdn.microsoft.com/de-de/library/s3f49ktz(v=vs.100).aspx

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel