When I don't know what a macro actually does, I compile a simple program and then read the "program list" following the addresses. For example try LCALL, PAGESEL, etc. Dennis Crawley Argentina ----- Original Message ----- From: "Ben Hencke" To: Sent: Friday, February 20, 2004 4:13 AM Subject: Re: [PIC:] Nested if macros > Does anyone know how MChip treats the extended > instruction set as single instructions? In the docs it > mentions that the extended instruction set are just > macros, but the debugger steps over them as if they > were single instructions (IIRC). It does this to even > the the instructions that have 2 equivelent > instructions listed. > > - Ben > > > --- "Alan B. Pearce" wrote: > > > This always has been a hassle. I suspect that MPLAB > > debugger just treats > > macros like they are high level language statements, > > and does not try to > > figure out what is inside the statement. I know it > > has always annoyed me > > when stepping through code, and when using Olin's > > macros, you tend to use a > > lot of them. > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail SpamGuard - Read only the mail you want. > http://antispam.yahoo.com/tools > > -- > http://www.piclist.com hint: To leave the PICList > mailto:piclist-unsubscribe-request@mitvma.mit.edu -- http://www.piclist.com hint: To leave the PICList mailto:piclist-unsubscribe-request@mitvma.mit.edu