On Tue, 13 Feb 2001, Rodrigo Araujo Real wrote:

>
>    Scott Dattalo wrote:
>    >You oughta grab gpasm. Several enhancements in the last few weeks make it almost 100% compatible with MPASM.
>    >In fact I was using tpasm, but I downloaded gpasm 0.8.15 and got these messages:
>    ...
>    Error FXM88.A16 265 : 103 parse error
>    Error FXM88.A16 283 : 103 parse error
>    Error FXM88.A16 341 : 157 maybe_evaluateCan't evaluate expression
>    Error FXM88.A16 341 : 157 maybe_evaluateCan't evaluate expression
>    ...
>
>    These errors repeated a lot, pointing to all lines that have labels like the one below.
>
>          GOTO    UM0707NA#v(i)
>
>    Is it because of the hash simbol?

It's a bug in gpasm. The good news is that Microchip has provided us with the
test files they use to test MPASM. Craig Franklin, a new member to the gpasm
team, has been tearing it up lately. He'll go through these files and figure out
where gpasm has defeciencies.

>
>
>    >As for the fixed point stuff, geez I wish I had time to help.
>
>    Could someone else give me a clue on that?
>    I tried to work with Q6.2 but it didn't work fine. Now I'm using the 1616
> routines and working with Q10.6 (that's what I really want), but the results
> are far from the expected.

Yeah, can some give Rodrigo some help!

Why don't you shed some light on what you're doing. You'll get 15 different
suggestions on how to do it better!

Scott

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.