On Tue, 25 Jan 2005, Olin Lathrop wrote:

> Ken Walker wrote:
>> Well, with it i don't get my declared EQU's in the watch window, and
>> without it i do ?????
>
> Why would you want to "watch" a constant?  Being constants, they don't
> change much.

I don't think he meant watching, but having them visibly available. I 
have had a similar problem with C and assembly, where one declares a 
symbolic constant, uses the symbol in the source, and later ends up with 
a listing to analyze a bug, and in the listing all constant instances 
are instantiated (with the data values) leaving one to scramble for 
printouts of relevant constants, trying to find out whether 0x12345679 
is MOVE_UP or MOVE_LEFT etc. This has happened to me at least once, and 
I actually used a script to replace the numeric constants with their 
symbolic values and analyzed the printout to find a bug.

imho there should be a way to make the constants 'survive' compilation 
and assembly and appear in the listings and in symbol tables (not as 
commented source lines - sometimes the compiled version of a statement 
is obscure enough that one cannot connect the source statement and the 
assembly even if printed one above the other - MCS51 compiler output 
with multibyte variables and constants comes to mind here).

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