[Octave-bug-tracker] [bug #60729] print_usage within classdef constructor breaks subsequent calls to the class

[Mike Miller]

Update of bug #60729 (project octave):

                  Status:                    None => Confirmed              
                 Release:                   6.2.0 => dev                    

    _______________________________________________________

Follow-up Comment #1:

Confirmed on the development branch.

Here is an even more minimal set of steps, with the same class example you
provided.


>> a = myclass ();
>> b = myclass (2);
>> [text, format] = get_help_text ('myclass');
>> b = myclass (2);
>> [text, format] = get_help_text ('/full/path/to/myclass.m');
>> b = myclass (2);
error: class not found: myclass
error: called from
    myclass at line 14 column 16


When 'get_help_text' is called on the full file name of the m-file containing
the classdef definition, it returns the help text, but it messes with the
behavior of the class definition already loaded into memory.

When it's called on just the short class name, it works fine.

    _______________________________________________________

Reply to this item at:

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

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