Excel Macros?

A few concerns...

• Norman has developed an Excel macro to convert a spreadsheet style register map into HDMC configuration and parts file for the CMM.
• A neat idea but I have a few concerns:
• Saving and sharing of source code: do we treat the Excel stuff as source code and store it in our CVS repository, so that others can use, and if necessary, modify it?
• If so, it introduces a non-Unix (and non-Makefile?) element into producing libraries and applications from source code.
• If not, the output from the Excel stuff is the stored source code and can them become out of step with the Excel input.
• Are there implications if we use this approach for some modules and not others? Eg multiple definitions of common registers (eg ModuleId)?