[Octave-bug-tracker] [bug #55501] subsequent calls to "help @sym/beta" gives "help beta" text

[Colin Macdonald]

Follow-up Comment #11, bug #55501 (project octave):

Maybe it depends on what you mean by "work" in "did they work with __which__
previously".

Octave 4.4.1:

octave:2> __which__ @pyobject/delete
ans =
  scalar structure containing the fields:
    name = @pyobject/delete
    file = 
    type = 

octave:3> __which__ @pyobject/pyobject
ans =
  scalar structure containing the fields:
    name = @pyobject/pyobject
    file = 
    type = built-in function




Now (without your patch):

octave:1> __which__ @pyobject/delete
ans =
  scalar structure containing the fields:
    name = @pyobject/delete
    file = 
    type = 

octave:2> __which__ @pyobject/pyobject
parse error near line 102 of file /home/cbm/src/pytave/@pyobject/pyobject.m

  external methods are only allowed in @-folders

>>>     dummy (x)
                ^



Things generally work better with methods implemented in their own m-files:

octave:5> __which__ @pyobject/fieldnames
ans =
  scalar structure containing the fields:
    name = @pyobject/fieldnames
    file = /home/cbm/src/pytave/@pyobject/fieldnames.m
    type = function

octave:6> __which__ @pyobject/fieldnames
ans =
  scalar structure containing the fields:
    name = @pyobject/fieldnames
    file =
/home/cbm/.octavehg/share/octave/5.0.1/m/miscellaneous/fieldnames.m
    type = function

I will try your patch later and see how this example behaves...


There are certainly problems about doc strings and classdef, e.g.,
https://savannah.gnu.org/bugs/index.php?48041

    _______________________________________________________

Reply to this item at:

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

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