Re: Another macro related issue- suspend/restore-interrupts vanishes when used in a macro word

>>>>> "Alex" == Alex Holden <[email protected]> writes:

Alex> Note that test2 compiles to a simple jump to criticalsection
Alex> with no calls to suspend/restore-interrupts around it:

This one was a tricky one, but with a simple one-liner fix, which is
now included in my development version. If you define a word in
metacompiler mode (such as suspend-interrupts, which by default does
nothing) then define it later in target mode (include picisr.fs
redefines a new word called suspend-interrupts), then in macro mode
only the first one was seen as the metacompiler was favored over the
target.

  Sam
-- 
Samuel Tardieu -- [email protected] -- http://www.rfc1149.net/sam