gnupic: gpasm-0.9.0


Previous by date: 9 Feb 2001 23:17:14 -0000 Re: gpasm-0.9.0, Nestor A. Marchesini
Next by date: 9 Feb 2001 23:17:14 -0000 Re: Graphical gpasm, Craig Franklin
Previous in thread: 9 Feb 2001 23:17:14 -0000 Re: gpasm-0.9.0, Nestor A. Marchesini
Next in thread:

Subject: RE: RE: gpasm-0.9.0
From: Craig Franklin ####@####.####
Date: 9 Feb 2001 23:17:14 -0000
Message-Id: <01020917243300.00809@r2d2>

I have fixed the problem in gpasm.  

It hasn't been throughly tested yet, but assuming it passes the tests, it will
be part of gpasm 0.9.1. 

On Fri, 09 Feb 2001, you wrote:
> Hello Craig
> 
> Excuse me for delay to respond,  now.... understanding because of the
> things...
> both methods to perform perfect, I utilize ERRORLEVEL
> , -.302, -.306,  -.226
> of lenguaje C,  I to stay learning with a book ttituled
> 
> Theacher Yourself C++ for Linux in 21 days
> ISBN 0-672-31895-4
> Sams Publishing
> 
> this is a "small book" of  1110 pages, the same to come a friend from Miami
> 
> well, step by step, gpasm will be better.
> Craig...thanks a millon !!!
> 
> greetings
> 
> Nestor A. Marchesini
> Chajari-Entre Rios-Argentina
> ICQ # 50983752 nick colo
> ####@####.####
> 
> > Another method to make the message go away is to suppress 226.
> >
> >   RADIX            HEX
> >   ERRORLEVEL 0, -.302, -.306,  -.226
> >   PROCESSOR  16F84
> >
> > The documentation has been updated.  The new version will be released with
> > gpasm 0.9.1, hopefully soon.
> > The new documentation wouldn't help you much.  The code for this one, 226,
> is
> > an UNKNOWN warning message.  Anything which hasn't been migrated from the
> old
> > error system to the new one or any error which is related to a known gpasm
> bug
> > are assigned UNKNOWN codes.  Sometime in the future all of these will be
> gone.
> >
> > This particular error has to do with the way gpasm parses the constants
> > in the errorlevel directive.  Currently, it assumes all numbers should be
> > interpreted based on the radix setting.  It shouldn't.  It should always
> > interpret the numbers in the ERRORLEVEL directive as decimal.
> >
> > The warning was a cheesey way for me to tell the users about the problem.
> A
> > comment to this effect is in the code.
> >
> >     if (state.radix != 10){
> >       gpwarning(GPW_UNKNOWN,"All codes must be proceeded by '.'
> Example: -.203");
> >       // BUG: Fix this and remove the warning!!  GPASM should always
> assume
> >       //      the arguments are decimal regardless of the current
> settings.
> >     }
> >
> > You can ignore the message.  It will still work properly because the "."
> forces
> > decimal.
> >
> > If you don't like seeing the message do the following:
> >
> >   RADIX            DEC
> >   ERRORLEVEL 0, -302, -306
> >   PROCESSOR  16F84
> >   RADIX            HEX
> >
> > This will be fixed in a future gpasm release.
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####

Previous by date: 9 Feb 2001 23:17:14 -0000 Re: gpasm-0.9.0, Nestor A. Marchesini
Next by date: 9 Feb 2001 23:17:14 -0000 Re: Graphical gpasm, Craig Franklin
Previous in thread: 9 Feb 2001 23:17:14 -0000 Re: gpasm-0.9.0, Nestor A. Marchesini
Next in thread:


Powered by ezmlm-browse 0.20.