Matt Shin

Wildcard syntax such as: ``` cfg build.prop{fc.flags}[*/foo/bar] = --some-option build.prop{fc.flags}[foo/bar/a*] = --some-other-options ``` can be useful for declaring multiple compiler options for a selection of name spaces.

From a user via email: > I'm just working through a sizeable list of conflicts, post merger, and it spurred an idea. > It would be really nice to have...

Now that the build system continues as much as possible, the error message from a compiler failure can be buried in the middle of the log. This can make it...

Consider an extract-build with inheritance. The original make has extracted the following targets: ``` foo.f90 bar.f90 baz.f90 ``` In its build, the user has explicitly excluded `baz.f90` with a `build.ns-excl`...

E.g.: - A code generator task may generate many targets. - A code generator task may take different build properties to generate a different set of targets.

E.g. Extract does not do the right thing if the user removes an item in a `use=DEST ...` statement in incremental mode.

In archive mode, we should TAR-GZIP targets generated by intermediate steps, e.g.: - everything under `extract/`. - everything under `preprocess/`. The complication is that they can be used as build...

Suppose we have something like this in a Fortran source file: ``` fortran use an_external_mod, only: a_subroutine ``` where `an_external_mod` is not part of the source tree. Normally, we'll just...

Currently, each location keyword is associated with a set of browser mapping configurations. It would be more desirable to have a set of mapping configurations for each server host instead.

Now that FCM revision keywords can be stored as a property at the HEAD of the project root, FCM should no longer insist on the requirement of a primary location...