Peter wrote:

> I post here since gpasm requires yet another mailing list
> subscription, which I do not have time to manage. I hope that this
> message will be forwarded to the gpasm maintainer(s).
>=20
> While using gpasm-0.14.1 (Mar  7 2012), a construct like:
>=20
> #ifdef SOME_SYMBOL
>   end
> #endif
>=20
> fails with an error message along the lines of '#endif expected' (at
> end). This is a bug imho, the #ifdef etc. is to be treated as a
> preprocessor directive as in C, and should issue at most a warning in
> this case. As it is, the feature prevents a test unit from being
> embedded in an asm file. The intent is to be able to assemble a test
> unit from the same source using a command line switch such as
> -DSOME_SYMBOL . The same unit can be assembled as subroutine/library
> without said symbol (or when defining another).

While I agree with your complaint in the essence of it, I don't see how
this would prevent what you're describing. Can't you put the #ifdef
bracket around the test code instead of around the end directive?

Gerhard
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.