gnupic@linuxhacker.org
gnupic@linuxhacker.org
Subject: Re: gpasm problem
From: Craig Franklin
Date: Tue, 08 Apr 2003 21:02:47 -0500
You found a bug in the lexer. I will get it fixed up and commited to
cvs. As a work around, switch one pair of numbers and the operator
inbetween and it will assemble ok.
> if ((1 > 0) || (10 > 30))
Tobias Schlottke wrote:
>
> Hi
>
> I just tried to recompile an old project and had a
> gpasm problem:
>
> With gpasm-0.10.0 I can compile the short code shown
> below with success.
>
> Using gpasm-0.10.4 and the current cvs version
> (gpasm-0.11.1 alpha) I get a parse error.
>
> Of course this snippet is nonsense. I reduced it to the
> critical part. The problem is the or'ed combination in
> the condition.
>
> 0.10.0:
> bug.asm:6:Message [301] Error!
> (which is correct)
>
> 0.10.4 and newer:
> bug.asm:5:Error [103] parse error
> bug.asm:5:Message [301] Error!
> bug.asm:6:Error [125] Illegal condition (ENDIF).
>
> -------------------------->8------------------------
> org 0
>
> initEE macro pointer
> if ((0 < 1) || (10 > 30))
> MESSG "Error! "
> endif
> movlw pointer
> endm
>
> initEE 0x40
> end
> -------------------------->8------------------------
>
> Any hints?
>
> Thanks,
> Toby
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: gnupic-unsubscribe@linuxhacker.org
> For additional commands, e-mail: gnupic-help@linuxhacker.org
gnupic@linuxhacker.org