Re: SPASM - a MPASM behave alike

On Sat, Jun 06, 2009 at 08:20:57PM -0400, David Barnett wrote:
> The problem with gpasm's "two pass" system is that it's sloppy about how it
> does the substitutions, and it does too much in the lexer. That makes it
> nearly impossible to do some things we need. For instance, if the
> indentation is wrong in the assembler syntax, gpasm gets completely tripped
> up and gives very strange errors because the lexer has to assume that
> anything in column 1 is a directive or label, without checking whether it
> corresponds to an opcode instead.

What would the challenges be in writing a completely standalone
preprocessor which just emits the processed assembly to be then fed
into gpasm?

-pete

---------------------------------------------------------------------
To unsubscribe, e-mail: gnupic-unsubscribe@...
For additional commands, e-mail: gnupic-help@...