On 4/4/23 09:00, jr wrote:
> my gcc is "elderly", and compilation fails, alas.  excerpt from build:

Yep. I think having a compiler not compliant to c++11 is the only way 
you can get that fail. I have in my head the configure program should 
kick out a warning if it cannot do certain c++11 things - those might 
not include the compile time asserts though.

Aside: All v3.8 releases, technically, require a c++11 compliant 
compiler - but there is fuzziness to be had for sure.

There is a configure script flag called: --enable-compile-warn which 
turns on a set of warnings (and turns off -w).

You can of course add more -wall -wextra come to mind as ones I run when 
just trying to clean up things a little - but I cannot find those notes 
at the moment...

Bill P.

Post a reply to this message