The bug is known and will be fixed in next release of MPASM (1.20).
     The beta release of this version should be on the MCHIPBBS in a couple
     of weeks or so.

     Thang


______________________________ Forward Header __________________________________
Subject: Re: MPASM problem
Author:  "Robinson, Peter John" <PRobinso@QITGSDV1.MS-MAIL.TELECOM.COM.AU> at
Internet_Exchange
Date:    5/25/95 9:40 AM


Mauricio

This is a bit of MPASM "functionality".  It doesn't like replacing
an opcode using a #define.  Arguments are ok but the opcode itself
fails.  You'll have to use a macro :-(  Microchip, if you're
listening, this would be a good one to have a look at.


>Hi there!
>
>I'am using MPASM 01.10 dated 27/01/95 and I have encountered a strange
>error, or better, mpasm behaviour. When I use the #define directive
>to define a 'new' instruction (see example code) mpasm reports:
>
>Error : Duplicate label (clc Inconsistent duplicate macro declaration)
>                        **********************************************
>
>#define clc bcf STATUS, C
>#define zero 0
>
> . . .
>        movlw  zero         ; ok
>        clc                 ; Error!
>. . .
>
>Does anybody have any similar experience, or any solution (other than
>defining a macro)?
>
>thanx,
>
>Mauricio CULIBRK
>
>ARNE Computers d.o.o.
>Cesta v Gorice 38                                   Phone:   +386 61
1233-171
>61111 Ljubljana                                     Fax:     +386 61
1233-488
>Slovenia                                            E-Mail:
 mauricio@arne.si
>E U R O P E