MikroElektronika Forum

Hi ME's

when we add a infinit loop inner main program, in this place the compiler understand that it loop
is the "end." of program. Compiler don't issue warning or errors but code stay truncated.
ofcourse that by logic the program never will go ahead but can be a programmer error or a simple
way to test at this point. i think that compiler never can missing the code after of loop and need
to terminate exactly at 'end.' statement.
I don't remember about this before.

Hi!

Compiler don't issue warning or errors but code stay truncated.

I'll inform our software developers regarding this issue. It will be considered.
Thanks!

MAN wrote:i think that compiler never can missing the code after of loop and need
to terminate exactly at 'end.' statement.

I'm of the same opinion. There's no need to outguess programmer's intentions - if one want's to skip part of code in compilation, one may do it easily by oneself. Code testing is indeed much harder when whole RAM & ROM organisation may change due to temporary insertion of an infinite loop.

Hi Janni;

janni wrote: Code testing is indeed much harder when whole RAM & ROM organisation may change due to temporary insertion of an infinite loop.

without doub, we never see what exactly was happened. This too put a "error" in the final .cof generated.
The .cof seem don't find the "end." statement too.

Tks slavisa;