[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #44934] classdef parser prints extra newline w
|
From: |
John W. Eaton |
|
Subject: |
[Octave-bug-tracker] [bug #44934] classdef parser prints extra newline when failing to parse bad classdef file |
|
Date: |
Wed, 17 Apr 2019 19:21:28 -0400 (EDT) |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 |
Follow-up Comment #4, bug #44934 (project octave):
I pushed the following changeset to fix this problem.
http://hg.savannah.gnu.org/hgweb/octave/rev/44d1fe403c19
I don't know exactly what the original problem was, but in the current
sources, the exclusive start state FQ_IDENT_START in the lexer wasn't
recognizing newline characters so they were just being passed through to the
output. Very confusing behavior to track down since I kept trying to find
where Octave was writing that to octave_stdout!
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?44934>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #44934] classdef parser prints extra newline when failing to parse bad classdef file,
John W. Eaton <=