Allow output of multiple binaries per module.

[ta0kira]

The main reason to allow this, vs. requiring one module per binary, is to allow multiple binaries to utilize the same private code, whether it's in the same .0rx or in $ModuleOnly$ sources. The current compromise would be to hide that code in a submodule with a name like internal.

This is probably an easy fix, but it will require turning CompileBinary into a list. Or, just making CompileBinary a separate object and then updating (and renaming) CompileIncremental to contain a list of CompileBinary.

[ta0kira]

Another option is to add a procedure pragma to indicate a function to use for a binary.

concrete MyBinary {
  @type run () -> ()
}

define MyBinary {
  run () { $CreateBinary["MyBinary"]$
    // ...
  }
}

The main issue here are:

• Potential name clashes between output names.
• Spreading out info about where the binaries are coming from.
• Needing to modify a source file in order to change the binary name or location.
• Aggregating all of the binary info for a module might be a little messy.

[ta0kira]

I'll reopen this if it turns out to be problematic.