GPasm include files

[Rob Hamerling-3]

I'm in a project for creating a script to produce header files for JalV2
from the MPLAB contents and I was curious how the GPASM header files
would have been created. So I was browsing through these files and I was
a little surprised to find in the .inc files of gputils comments like:

>  Note that the processor must be selected before this file is
>  included.  The processor may be selected the following ways:
>
> 1. Command line switch:
>         C:\ MPASM MYFILE.ASM /PIC16C621
> 2. LIST directive in the source file
>         LIST   P=PIC16C621
> 3. Processor Type entry in the MPASM full-screen interface

I would think this should be 'GPASM' in stead of 'MPASM'.

(hair-splitting is one of my 'hobbies'...)

Regards, Rob.

--
Rob Hamerling, Vianen, NL (http://www.robh.nl/)

---------------------------------------------------------------------
To unsubscribe, e-mail: gnupic-unsubscribe@...
For additional commands, e-mail: gnupic-help@...

[Robert Pearce-3]

On Sunday 06 July 2008, Rob Hamerling wrote:
> I would think this should be 'GPASM' in stead of 'MPASM'.

Only if you rashly assume that gpasm has its own unique set of include files.
Given that the aim is to be 100% mpasm source compatible, it actually makes a
lot of sense to ship with unmodified mpasm headers. Check a few lines above
and you'll see the header has a Microchip Technology, Inc. version /
copyright tag.

Rob

---------------------------------------------------------------------
To unsubscribe, e-mail: gnupic-unsubscribe@...
For additional commands, e-mail: gnupic-help@...