??? 06/08/07 09:18 Modified: 06/08/07 09:18 Read: times |
#140411 - tool-independent approach Responding to: ???'s previous message |
Andy,
even if we don't know the particular toolset, there are ways how to achieve this and make it tool-independent. In fact, there are situations when this is simply unavoidable. Most assemblers have a straight include statement (and C does have it, too). So, the constants can be simply included from an external file, simply one constant per file and nothing more. If the assembler can't include the content of file within a line (i.e. would require end-of-lines before/after the include statement), a simple "cat" or "copy" within a script/batch file will remedy it, producing an intermediate file with the required assembler pseudocode (such as db). If the constants are desired to be all in one file, some sort of preprocessing which splits this file up would be needed, but that's relatively easy. 0.02SKK (practically zero) JW |
Topic | Author | Date |
Constants as extern | 01/01/70 00:00 | |
Insufficient Information | 01/01/70 00:00 | |
tool-independent approach | 01/01/70 00:00 | |
Preprocessing | 01/01/70 00:00 | |
Example | 01/01/70 00:00 | |
RTFM? | 01/01/70 00:00 | |
Here is one way to do it | 01/01/70 00:00 | |
Thanks a lot![]() | 01/01/70 00:00 |