[Octave-bug-tracker] [bug #56032] Weird "if" parsing behavior ignores stuff past first expression in some cases

[Andrew Janke]

Follow-up Comment #1, bug #56032 (project octave):

Simpler repro:


>> if 1 > 3 klsdjfkldsjfkls; else fprintf('nope\n') end
nope


Maybe the "if" stops executing its conditional as soon as it hits a full
expression, and treats stuff following that as part of the code to execute if
the conditional is true?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?56032>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/