[Scons-users] Fortran Scanner and #include

[Bill Deegan]

Luke,

Here's one wiki page:
https://github.com/SCons/scons/wiki/GitWorkflows

Basically, you'll make your change, you'll have to update or add a test,
add a blurb to src/CHANGES.txt and if applicable update the documentation.
Feel free to come ask questions on IRC or on the #devel channel on our
discord server(more people there lately).

-Bill

On Fri, May 1, 2020 at 12:14 PM Luke Robison <lukerobison at gmail.com> wrote:

> I noticed that the Scanners.Fortran module does not pick up dependencies
> to files which are "#include"-ed in the original source.  This is a pretty
> trivial thing to add, since there is support for the "include" statement,
> and the addition of "#?" to the pattern makes it easily match both INCLUDE
> and #include lines.
>
> The only argument against adding that I can see is that #include is
> technically a c-preprocessor statement, as such it differs from INCLUDE in
> the following way: #include IS case sensitive, #include MUST come at the
> beginning of the line and #include ONLY applies when the preprocessor is
> running (-cpp flag or .F/.F90 files).  Practically speaking, if any of
> these constraints are not met SCons will assume a dependency when there is
> none, but the compiler will probably error-out.
>
> If agreed, how can I best submit a patch for this change?
>
> Luke
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20200501/8b70e2bf/attachment.html>