>
>
>>
>>Waiting for a new compiler usually delays release for 3 or 4 weeks. I don't
>>have issue with this, but I'm not sure it would worth it. Is there any "deal
>>breaker" bugs in current release ?
>>
>>There's a bug which annoyed me a lot for quite some time:
>I've had a look again at the actual report, the fragment which did not work on
>a PIC18F26K22 was
var word tunables[16]
var byte counter
for 16 using counter loop
tunables[counter]=data_eeprom_word(counter*2)
end loop
I had to work around it like
var word temp
for 16 using counter loop
temp=data_eeprom_word(counter*2)
tunables[counter]=tempend loop
Another line which drove me crazy was
if ((x>12)&(x<29)&((number*3)==(y+35))) then...
which just wouldn't evaluate correctly. It's probably the same bug to blame
here, the workaround would likely be to use a temp variable storing (number*3).
I don't mind releasing with the old compiler, just thought to briefly think
about that.
Greets,
Kiste
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/jallib?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
