gnupic: Re: [gnupic] gpasm macros/defines
Subject:
Re: [gnupic] gpasm macros/defines
From:
"David Barnett" ####@####.####
Date:
17 Nov 2006 22:47:11 +0000
Message-Id: <09cb01c70a9a$4ec56870$0401a8c0@barnett2>
----- Original Message -----
From: "David Barnett" ####@####.####
To: ####@####.####
Sent: Wednesday, October 18, 2006 3:55 PM
Subject: Re: [gnupic] gpasm macros/defines
> ...
> With the other problem, I might be able to combine assembler variables and
> #defines to work around it...
>
> Is there any good reason for not expanding macro parameters in define
> statements contained within the macros? Or is there some kind of standard
> that unambiguously defines the correct behavior?
I thought I had a workaround for this define/arg expansion problem:
START1 MACRO X
#define OP1 movlw X
ENDM
...
START1 5
OP1 ; gpasm reports "symbol not previously defined (X)."
but it turns out there are problems with it, too. I'm getting kinda
desperate for advice here. Scott, have you gotten in deep enough with
gputils to know anything about this?
David
