gnupic: __config directive w/16f628a


Previous by date: 17 Apr 2004 20:45:01 +0100 Re: gpasm chokes on #IF, David Willmore
Next by date: 17 Apr 2004 20:45:01 +0100 Re: gpasm chokes on #IF, Craig Franklin
Previous in thread: 17 Apr 2004 20:45:01 +0100 Re: __config directive w/16f628a, Craig Franklin
Next in thread:

Subject: Re: __config directive w/16f628a
From: Craig Franklin ####@####.####
Date: 17 Apr 2004 20:45:01 +0100
Message-Id: <1082231071.4393.7.camel@r2d2>

On Sat, 2004-03-20 at 20:18, Craig Franklin wrote:
> On Sat, 2004-03-20 at 02:47, Pete wrote:
> > Hello. Has anyone had trouble using the __config directive with the 16f628a 
> > and gpasm-0.12 ? I tried to compile the following and get this error:
> > int_osc.asm:24:Error [103] parse error
> > It does compile with mpasm. If I change the chip to plain 16f628 gpasm will 
> > compile it also. Have tried different config statements also. Appreciate any 
> > suggestions, Thanks Pete.
> 
> It is not a problem with config or the processor.  There is an error in
> the include parsing.  As a work around, insert a blank line after the
> include.  I will fix this later tonight.
> 

I was wrong.  There isn't a bug in gpasm's include parsing.  Some of the
header files from Microchip are malformed.  They are missing a newline
before the EOF.  We have had this problem before.  I will start checking
the files for this condition from now on.  vi will detect and fix this
problem.


Previous by date: 17 Apr 2004 20:45:01 +0100 Re: gpasm chokes on #IF, David Willmore
Next by date: 17 Apr 2004 20:45:01 +0100 Re: gpasm chokes on #IF, Craig Franklin
Previous in thread: 17 Apr 2004 20:45:01 +0100 Re: __config directive w/16f628a, Craig Franklin
Next in thread:


Powered by ezmlm-browse 0.20.