> With JalV2 2.4o-beta many samples of yours give warnings,
> most of which I don't understand ('condition is always true'
> on a line with 'end loop')!
In assembly, the stop condition of a loop is always checked at the end of the
loop, so if it's something like
while byte(variable) <300 loop
[...]
end loop
the line with "end loop" actually translates to that check that is always true.
Of course it would be better to point the warning to the place where the
comparison is in jal code, but at least that could be the reason why "end loop"
can be called a "condition".
Greets,
Kiste
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en.
