Index
> Compiler Internals > causing error at certain stages of compilation |
| Author |
|
|
Tomasz Grysztar 14 Sep 2006, 10:34
Over time I successively got rid of parser stage errors, to make the separation of this stage from assembler "transparent". The language rules, as I'm now defining the in Understanding fasm article etc. do not define parser as a separate being. It's existence is only an internal optimization of fasm that generally should not affect the visible behavior of the compiler.
The "illegal instruction" and "symbol already defined" errors are an examples of immediate-termination assembler errors. They are signalized immediatelly when they're encountered. As for causing error during a given pass, you may try the tricks like: Code: if ~xxx display 'pass 0' else if ~yyy display 'pass 1' ; for example, put some illegal instruction here else ;... end if yyy = 1 end if xxx = 1 |
|||
14 Sep 2006, 10:34 |
|
|
vid 14 Sep 2006, 11:46
nice trick... hehe, implementing it as macro seems harder than i thought
Quote: The "illegal instruction" and "symbol already defined" errors are an examples of immediate-termination assembler errors. They are signalized immediatelly when they're encountered. thanks |
|||
|
14 Sep 2006, 11:46 |
|
< Last Thread | Next Thread > |
Forum Rules:
|