It may seem like a trivial issue, but the lack of a clear standard and rationale is making it difficult to expand the system. The module system can help, but (at least) the following issues remain:|
* Names for user-configurable settings. Remember that Jam initially imports all names from the environment (see Environment Variables, then overwrites those with settings from the command-line. At least one person has argued quite strenuously in favor of ``namespacing all variable names with a prefix, e.g. ``BOOST_. The use of site-config.jam (see the design section below) ought to make this less of an issue.
* Names for rules. My inclination is to use a different naming convention from Perforce Jam (MixedCase??) just so there's little danger of overwriting the built-in rules and causing an incompatibility with older Jam files.
* Dashes or underscores for separating words? Dashes are much easier to type, but I've recently found a few bugs because I put an underscore where a dash belonged.