Better code check before compile?

[HenrikOlsson]

You may have found something you did not know and it IS something to be aware of but it's not a bug. It's like that by design.
It's all covered in details thru out section 7.6 in the manual - read it ;-)

/Henrik.

[Ioannis]

It is common to other languages too like C for example.

Ioannis

[HenrikOlsson]

And the compiler is really only able (if so designed) to catch out-of-bounds error when you have a static index like that MAS[10]=20 but in many cases you're using an index variable like MAS[x]=20 and then there is no way for the compiler to know what x is going to be at runtime.

On your typical 80's computer running BASIC, like the ZX Spectrum referenced earlier, the execution was interpreted so the interpreter could catch out of bounds errors during execution. PBP isn't interpreted but say it was or that it in some other way COULD detect that out-of-bounds error - what should happen?

[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