[Octave-bug-tracker] [bug #44934] get_help_text issues two error messages when failing to parse classdef file

[Rik]

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

                 Summary: get_help_text issues two error messages when failing
to parse classdef file
                 Project: GNU Octave
            Submitted by: rik5
            Submitted on: Sun 26 Apr 2015 10:19:46 PM PDT
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

This is a bit involved, but there appears to be an error in the way
get_help_text and parsing of classdef files with errors are done.

The set-up is to have DocSimpleDouble.m in the current directory (".").  Also
in the current directory is the script tst_try.m.  Run tst_try and you will
get two newlines ahead of the final retval for the function.  See below


>> tst_try


ans =  1
>> 


When I run tst_try under 3.8.2 there are no extra newlines.

The newlines aren't such a big deal, but they seem to be indicative of a
bigger problem.

If I run the failing line of tst_try in the dev version of Octave I get


>> get_help_text ('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
                                 ^


error: function, method, class, and package names may not be keywords
parse error near line 1 of file ./DocSimpleDouble.m

  syntax error

>>>    methods
                                 ^

>> 


What is odd is that there are two errors produced.  It is as if the
error_status variable is getting set, but no one is checking it and
get_help_text in corefcn/help.cc is continuing.  3.8.2 does the same thing,
i.e., it produces two error messages.  But it doesn't produce two newlines in
tst_try.m






    _______________________________________________________

Reply to this item at:

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

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