Well, I'm probably missing something (or everything), but
it seems to me
that the following compiled code layout could solve the problem:
JUMP to A IF false
... # first true instruction
...
... # last true instruction
JUMP TO B
A: ... # first fals
Hm, was my first Idea also,
but why is condition evaluated a second time ONLY if it is TRUE on the
first run?
I have looked into the source, but was not sure of it's a problem of the
resolving ... or maybe of the parser?
--
Jochen
Sam Tregar schrieb:
On Fri, 8 Jul 2005, Jochen C
Hi,
i found a nice bug (that keeps me awake for about 3 hours...)
I have the following template:
YES
NO
which is not that complicated.
When you run the program, and the expr is evaluated to FASLSE then there
is no problem and you get
NO
in the outut.
BUT (!) if the expr is TR
