Under linux on x86_64, the long type is 8 bits. Why do we disable FT_LONG64?
/* A 64-bit data type will create compilation problems if you compile*/
/* in strict ANSI mode. To avoid them, we disable its use if __STDC__ */
/* is defined. You can however ignore this rule by defining
Under linux on x86_64, the long type is 8 bits. Why do we disable
FT_LONG64?
/* A 64-bit data type will create compilation problems if you compile*/
/* in strict ANSI mode. To avoid them, we disable its use if __STDC__ */
/* is defined. You can however ignore this rule by
What kind of compilation problem would the long type cause?
... not to mention that 'long long' is standard since C99. Which
compiler still has problems with that?
ANSI is not C99 :-)
AFAIK there *are* still compilers (mainly for embedded systems and the
like) that don't support C99.
On Wed, Aug 20, 2014 at 10:20 AM, Werner LEMBERG w...@gnu.org wrote:
Under linux on x86_64, the long type is 8 bits. Why do we disable
FT_LONG64?
/* A 64-bit data type will create compilation problems if you compile*/
/* in strict ANSI mode. To avoid them, we disable its use if
On Wed, 20 Aug 2014 10:40:07 -0400, Alexei Podtelezhnikov said:
Even if you are serious, 'long' is 8 bits under both linux and OS X on
64-bit platforms.
8 *bytes*. :)
It is nuts to beg for it with
FT_CONFIG_OPTION_FORCE_INT64 these days. It should be quite the
opposite. People should ask to
It is nuts to beg for it with FT_CONFIG_OPTION_FORCE_INT64 these
days. It should be quite the opposite. People should ask to disable
it if they are stuck in the last century without 'long long'
support.
+1.
Changing the default is OK with me.
Werner
