[Info-vax] C and C++ and clanger-free clanging

[Stephen Hoffman]

On 2019-07-04 14:50:09 +0000, Dave Froble said:

> Well, where else would one reasonably put such?

Where else?  On OpenVMS, in the build procedures.

That's fairly common, too.

Either a procedure written in DCL that builds the specific source file 
or specific executable, or the whole show.

Or if not in DCL, as some of the data invoked by one or more of the 
various make tools; mms/mmk/gmake/etc.

On other platforms, the settings can be stored in the project database 
file that's used to build the whole project.

Which is really handy in various ways, and can sometimes be very opaque 
in other cases.

Or there's the ever-popular forest of logical names.  🙄

> Different programs may have different needs, and should those 
> re-compiling the programs have to remember how to do so?  Much better 
> to just place the requirements inside the programs.
> 
> Maybe some day C and such will learn how to do so?
> 
> Nah, I'm just dreaming ....
> 
> PS - and don't tell me it already can, I just don't care ...

Embedding the settings directly into the source code tends to be 
somewhat brittle.

Works well, right up until you're dealing with architecture-specific or 
build-specific or version-specific 
switches/controls/settings/qualifiers.

I've used the C preprocessor to build Fortran code, as have various 
other folks.




-- 
Pure Personal Opinion | HoffmanLabs LLC