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

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

[Octave-bug-tracker] [bug #57924] Comment not treated as a comment when


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #57924] Comment not treated as a comment when it has unbalanced parentheses or brackets
Date: Sat, 29 Feb 2020 15:52:19 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.122 Safari/537.36

Update of bug #57924 (project octave):

              Item Group:        Incorrect Result => Regression             
                  Status:                    None => Confirmed              
                 Release:                     dev => 6.0.90                 

    _______________________________________________________

Follow-up Comment #1:

Confirmed on the default branch and on the version 6 stable branch. This is
certainly weird behavior, but only affects comments entered on the command
line.

The comment is treated as a comment, but the open bracket or parenthesis is
also causing the lexer to look for more input on the next line.

This may have also broken block comments (with '#{' and '#}') entered on the
command line, although the broken behavior is slightly different.

This may have something to do with a recent change to the lexer to fix
continuation lines within open arrays
(https://hg.savannah.gnu.org/hgweb/octave/rev/1db62b2d6c39).

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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