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

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

[Octave-bug-tracker] [bug #65220] get_help_text returns docstring from p


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #65220] get_help_text returns docstring from parent methods
Date: Tue, 30 Jan 2024 10:26:39 -0500 (EST)

Follow-up Comment #18, bug#65220 (group octave):

"i didn't run through all 2^7 options"

BUT wait, I wanted to see *all* possibilities!

So, for methods, it always grabs the comment inside the function, correct?

But for the constructor, it depends on whether there is a comment prior to the
"classdef" keyword?  Am I getting that right?

I'm a bit confused by


now, removing the main 'prior' one and doing a clear -c:

    >> help foobar_class
      comment inside classdef block

    >> help foobar_class.foobar_class
      comment inside classdef block


and then


replacing it but removing 'inside method'

    >> help foobar_class
      comment inside classdef block

    >> help foobar_class.foobar_class
      comment inside constructor


In one case, "help foobar_class.foobar_class" returned the comment outside the
constructor function and in the other case it did not?  Did you clear the
class definition each time?

Maybe I should just post a full set of files and a complete script to run so
that there is no confusion about whether "clear -c" was used?

Also, WTF is up with the output


>> help foobar_class.meth
foobar_class/meth is a function.
    meth(obj)


I was hopeful we were done with any syntax like "@cls/meth".

Does "help foobar_class/meth" work?



    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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