Zinn wrote:Why should DevMake insert into another Dev module? Just left it by a module of its own.
- Helmut
Well, I also thought about this possibility.
Here are the detail problems:
You would need a new docu file, with just a single command.
You would need to update the build tool.
You would need to update the "Map to the Dev Subsystem" (where else are possible inconsistencies?).
You would (slightly) slow down recompilation of the system.
You would add a very small module to the existing small module DevCompiler.
You would separate things that are closely related.
This is not only a migration tool but a general purpose command for development.
It plays together with "Compile Module List". One command provides the input for the other.
To me it is most naturally hosted in DevCompiler and the changes are much simpler this way
and there is no danger of introducing any inconsistencies.
Also if you look into the implementation: it is so similar to the things done in DevCompiler anyway
and the import list is almost completely a subset of DevCompiler's import list.
In addition, it would be well-prepared for later extension e.g. towards another command
(CompileSubsystems) that does a recompile instead of generating a list. But I am not proposing to add this now.
- Josef
