gnupic: symbols name and gpasm
Subject:
Re: symbols name and gpasm
From:
Craig Franklin ####@####.####
Date:
27 Nov 2004 00:51:16 +0000
Message-Id: <41A77BD4.2000102@users.sourceforge.net>
Gibaud Alain wrote:
>Hi,
>
>Is there any drawback to use exotics characters such as
># or @ in symbols name under gpasm ?
>
>
I can't think of any big drawbacks.
Depending a persons background there may be some confusion. For
example, many people would expect a label starting with "#" to be a
preprocessor directive. They would figure it eventually.
>I try them and gpasm seems to be happy.
>(For obvious reason, $ is rejected).
>However I am not sure it is a good idea, because they are not
>explicitly specified as valid by gpasm documentation.
>
>
The manual needs to be updated. It is missing some of the special
characters. It is also missing gpasm's support for the extended ASCII
character set (8 bit characters).
>Are these characters reserved in any way ?
>(Craig ?)
>
>
You found the obvious one ($). Also #v() is expanded in the lexer. You
aren't likely to have a problem with it. There are a few new coff
directives that start with "." Each of these cases is covered in the
manual.
There is a good chance that gpasm doesn't support some special
characters that mpasm does. A couple of months back I had to add some
missing ones, but I never found a complete list from Microchip.
>Alain
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ####@####.####
>For additional commands, e-mail: ####@####.####
>
>
>
>
