Chen Xiao Fan writes:
 > 
 > > -----Original Message-----
 > > From: piclist-bounces@mit.edu 
 > > [mailto:piclist-bounces@mit.edu] On Behalf Of Bill Freeman
 > > 
 > > gpasm the following code assembles fine for me:
 > > --------------------------------------------------------------
 > > 	processor 16C71
 > > 	ifdef __16C71
 > > 	include "p16c71.inc"
 > > 	__config _XT_OSC & _WDT_OFF & _CP_OFF & _PWRTE_ON
 > > ramtop  set 0x0C
 > > 	endif
 > > 
 > > 	; data storage needed for delays and general purpose
 > > 
 > > 	cblock ramtop
 > > 	endc
 > > 	end
 > > --------------------------------------------------------------
 > > 
 > 
 > You are of course correct and the above code is okay for
 > both gpasm and MPASM. And maybe it is good to have this
 > for multiple MCU.
 > 
 > Still I would like to point out that more "standard" way 
 > to define the processor for MPASM is like the following 
 > (from the MPLAB template). gpasm is happy with it as well.
 > 
 >   list      p=16c71       ; list directive to define processor
 >   #include <p16c71.inc>   ; processor specific variable definitions

	Yes, certainly.  That is the way that I would usually do it.
I was merely trying to remain as close as possible to the original
poster's problem code.  He used the processor directive, which I had
not known about, so I did too (though I had to put it outside of the
ifdef).

	Similarly, the original poster used double quotes as opposed
to angle brackets around the include file name, so I kept them.
Indeed, the angle brackets are a long standing convention for
system-wide, rather than project specific, includes.

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