octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #56032] Weird "if" parsing behavior ignores st


From: Andrew Janke
Subject: [Octave-bug-tracker] [bug #56032] Weird "if" parsing behavior ignores stuff past first expression in some cases
Date: Sat, 30 Mar 2019 06:04:40 -0400 (EDT)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36

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

                 Summary: Weird "if" parsing behavior ignores stuff past first
expression in some cases
                 Project: GNU Octave
            Submitted by: apjanke
            Submitted on: Sat 30 Mar 2019 06:04:39 AM EDT
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Other
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

This shouldn't work, right?


function blarg
  x = 1;
  y = 2;
  if x > y sldkfjdskljfskldklsdjf (x>y)
    fprintf('yup\n');
  else
    fprintf('nope\n');
  endif
endfunction


But it does this:


>> blarg
nope


The parentheses in the condition following the bogus keyword are significant.
If you remove them, you get a syntax error, like I'd expect.

Happens in 4.2, 4.4.1, and 5.1.0.





    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]