Re: heads up RE autoconf C23 vs legacy code

> I'm not blaming them.  Just saying that as soon as there was a new C std
> that rejected programs that were valid under a previous std, it becomes
> a bug not to document what langauge the program is in.
Yes, but what if at the time the source was touched for the last time, there 
was only C?

EF> Unfortunately, there's no #pragma language-level. In Perl, I simply write
EF> 	use 5.42;
EF> (and use feature 'foobar';)
EF> in the source to document which Perl exactly I write in.

GDT> Yes, but most invocations of a C compiler in practice support --std=cnn,
GDT> and build systems should try that and add it if it works.
The difference is that in Perl, I document the language variant in the source 
file written in that language, not in the build system.

> I don't see this as being about PKG_DEVELOPER.
I'm afraid the initial fall-out could be so massive that you get push-back 
for the idea.