view CITATION @ 19823:b2c4f869ff7c

fieldnames: fix for java objects from dynamic classpath (bug #42710) * fieldnames.m: this function supports passing a java class name as input instead of a java object. org.octave.ClassHelper.getFields() is capable of accepting both a java object or a java class name. However, it would get confused if the object is a java string. I will guess this was the reason to always pass the java class name to it. However, it seems that it will only accept java class names on the static classpath, which made the whole function failing when passing objects. The function will still fail if input is the classname of a class in the dynamic classpath though, but at least will now work if an object is used.
author Carnë Draug <carandraug@octave.org>
date Sun, 22 Feb 2015 19:21:18 +0000
parents a6d13c62fccf
children
line wrap: on
line source

To cite GNU Octave in publications use:

  John W. Eaton, David Bateman, Søren Hauberg, Rik Wehbring (2014).
  GNU Octave version 3.8.1 manual: a high-level interactive language for
  numerical computations.
  CreateSpace Independent Publishing Platform.  ISBN 1441413006,
  URL http://www.gnu.org/software/octave/doc/interpreter/

A BibTeX entry for LaTeX users is:

  @book{,
    author    = {John W. Eaton, David Bateman, S\oren Hauberg, and Rik Wehbring},
    title     = {{GNU Octave} version 3.8.1 manual: a high-level interactive language for numerical computations},
    publisher = {CreateSpace Independent Publishing Platform},
    year      = {2014},
    note      = {{ISBN} 1441413006},
    url       = {http://www.gnu.org/software/octave/doc/interpreter},
  }

We have invested a lot of time and effort in creating GNU Octave, please cite it
when using it.  See also `citation pkgname' for citing Octave packages.