[Octave-bug-tracker] [bug #44934] classdef parser prints extra newline when failing to parse bad classdef file

[Rik]

Update of bug #44934 (project octave):

                 Summary: try/catch prints extra newline when parsing bad
classdef file => classdef parser prints extra newline when failing to parse
bad classdef file

    _______________________________________________________

Follow-up Comment #3:

The actual error when trying to instantiate an object from class
DocSimpleDouble is


x = DocSimpleDouble

error: function, method, class, and package names may not be keywords
parse error near line 1 of file
/home/rik/wip/Projects_Mine/octave-dev/DocSimpleDouble.m

  syntax error

>>>    methods


If I change the first line of DocSimpleDouble to


classdef DocSimpleDouble < methods


Then I get the nearly the same message, but there is no newline between the
entering of the command and the line which begins with "error:".  This also
works with tst_try.


octave:5> x = DocSimpleDouble
error: function, method, class, and package names may not be keywords
parse error near line 1 of file
/home/rik/wip/Projects_Mine/octave-dev/DocSimpleDouble.m

  syntax error

>>> classdef DocSimpleDouble < methods


So maybe the problem is something in the classdef parser rather than
try/catch.  Re-titling again.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44934>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/