Re: workarounds around GCC miscompilation

Hi Jörg,

> Just names. Perhaps "HACK:" as a prefix in the one-liner log message would be
> enough to raise attention.

Whereas I thought about mentioning these things in the advice for porters file,
namely unix/PLATFORMS...

> Likewise, I felt uncomfortable about this log message:
>  < Make intparam.c compile with g++ >= 6.
> -> Make intparam.c compile with g++ >= 6. The "auto" specifier changed with C++11.
> Intparam and g++ 6 are symptoms -- or noise. "auto" is the root cause.

Yes, "auto" is the root cause. But root cause analysis and other technical
explanations belong in comments. A log message should indicate what has changed
(from the point of view of the user). In this case: intparam.c did not compile
and now it compiles again.

> in C++14 because of the redundancy: either you write e.g. int i =..., or you
> let the compiler derive the type, and write auto i = ...;

Thanks for explaining. They have reused a keyword to mean a completely different
thing. As usual in C++... Whereas in C# and Java it's called 'var'.

Bruno


------------------------------------------------------------------------------
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