[Octave-patch-tracker] [patch #9056] documentation for Java methods and fieldnames

[Mike Miller]

Follow-up Comment #5, patch #9056 (project octave):

The doc string for fieldnames.m already mentioned struct arguments. The only
change you made was to change "When the input is a structure" to "If the input
is a structure".

So I think we are both content with fieldnames.m.

I think it's fine to try to unify doc strings to make them more alike, when
they actually are. But fieldnames and methods are not really alike, one is
primarily meant for struct arguments and one is primarily meant for objects
and classes.

The behavior of fieldnames taking a string that is the name of a Java class
is, as far as I can tell, an Octave special-case extension. The main purpose
of fieldnames is to operate on structs or objects that can be cast to a
struct.

I think the right documentation for methods() is to treat Octave objects and
Java objects as the same thing, there should be no need to distinguish between
an Octave object or a Java object (or a Python object).

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/patch/?9056>

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