RFC: INCLUDE, #include and preprocessing

[Daniel Franke]

On Thursday 14 August 2008 23:34:42 Daniel Franke wrote:
> every so often the question pops up, whether INCLUDEd files should be
> preprocessed or not (of course, #include'd files are preprocessed). Usually
> people disagree whether it's a bug or a feature that gfortran does not
> preprocess INCLUDEd files. Most recently in PR37032.
>
> To resolve the situation, I'd like to ask you, gfortran maintainers and
> users, to find a consent whether this a bug or feature. The final decision
> should be documented as a reference for further PRs -- whether to close
> them as invalid or as dupe.

After four days, the vote bug vs. feature is 5:0.

Please find a corresponding update of the docs attached.
Tested with dvi, html and pdf targets. Ok for trunk?

Regards

	Daniel

P.S.
On Friday 15 August 2008 18:40:47 Janne Blomqvist wrote:
> Now that gfortran uses libcpp, perhaps it has some inquiry function to 
> find out the standard path?

Nothing as fancy as that, but there is a global variable 
(cpp_include_defaults) which is provided/used by gcc itself and is available 
in libbackend.a.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gfortran-include-file-handling.patch
Type: text/x-diff
Size: 1174 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/fortran/attachments/20080818/aef4b885/attachment.bin>