gnupic: Does #include directive working ok in gpasm?


Previous by date: 31 Jul 2002 12:24:46 -0000 Re: GPASM Compilation Error, Scott Dattalo
Next by date: 31 Jul 2002 12:24:46 -0000 PIC and TLVP programmer, Karel Polak
Previous in thread: 31 Jul 2002 12:24:46 -0000 Does #include directive working ok in gpasm?, Antonio A Todo Bom
Next in thread: 31 Jul 2002 12:24:46 -0000 Re: Does #include directive working ok in gpasm?, Craig Franklin

Subject: Re: Does #include directive working ok in gpasm?
From: Scott Dattalo ####@####.####
Date: 31 Jul 2002 12:24:46 -0000
Message-Id: <Pine.LNX.4.44.0207310506330.17742-100000@ruckus.brouhaha.com>

On Tue, 30 Jul 2002, Antonio A Todo Bom wrote:

> I tried to use gpasm version 0.10.3, in a actulaly developing project, just typing:
> 
> gpasm -p p16f628 filenam.asm

could it be that filenam should be filename?

AFAIK, No one has reported this kind of problem. I suggest you simplify 
your code to the point where only this behavior is exhibited.

There was one bug about 2 years ago where a non-ASCII character in a 
symbol name was confusing the gpasm parser, but that has been fixed. But 
there may still be a similar bug lurking.

Scott


Previous by date: 31 Jul 2002 12:24:46 -0000 Re: GPASM Compilation Error, Scott Dattalo
Next by date: 31 Jul 2002 12:24:46 -0000 PIC and TLVP programmer, Karel Polak
Previous in thread: 31 Jul 2002 12:24:46 -0000 Does #include directive working ok in gpasm?, Antonio A Todo Bom
Next in thread: 31 Jul 2002 12:24:46 -0000 Re: Does #include directive working ok in gpasm?, Craig Franklin


Powered by ezmlm-browse 0.20.