Better code check before compile?

[CuriousOne]

Yes the example I have is static, not runtime occurrence.

[CuriousOne]

---

Found another "bug" - if you put more DATA lines in code, than size of built-in eeprom, it will compile without errors, but PicKit 3 programmer will show you "Warning: Hex file loaded is larger than device."

[Ioannis]

Interesting... This is easy to check I guess.

Ioannis

[CuriousOne]

I made a typo, putting = instead of -

hpwm 2,rmd*rmd=1,20000

This statement does not produce any errors, as it should. Also, RMD value remains the same

[CuriousOne]

Found another.

Here is sample code, both variants should work same, but they don't

if ticker>150 and ard<140 and atrig=0 then
ticker=1 
atrig=1 
endif

This one is fine, but this one:

if ticker>150 and ard<140 and atrig=0 then ticker=1: atrig=1

is not - atrig is always set to 1, no matter if ticker and ard values are as defined in if-then thing. It looks like that code after : is handled as separate code, not part of if-then. But, if I add say GOSUB XX after it, it is executed.

[pedja089]

That is not bug. That way should work. This : is same as new row.
So this line

if ticker>150 and ard<140 and atrig=0 then ticker=1: atrig=1

is same as this

if ticker>150 and ard<140 and atrig=0 then ticker=1

atrig=1

I'm using PBP since 2004. And I found only one bug in pbp, and encounter multiple in MPASM.... DT helped me a lot to track bug to MPASM...

[CuriousOne]

no, it is not, because if I add GOSUB statement, it is being triggered on IF-THEN condition only.