Mercurial > octave-nkf
view .hgignore @ 19857: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 | dc76e3909d36 |
children | c16c446204e5 |
line wrap: on
line source
syntax: regexp # The recurrent (^|/) idiom in the regexps below should be understood # to mean "at any directory" while the ^ idiom means "from the # project's top-level directory". # gnulib makes these silly backup files .~$ # This directory gets created by gnulib during the build. # It contains no Octave files. ^libgnu/* # This directory mostly contains cruft during build time, but it does # contain some Octave code, so we gotta be a bit more careful about # what we ignore here ^m4/(?!ax_).+\.m4$ # Emacs tools create these (^|/)TAGS$ (^|/)semantic.cache$ (/|^)Makefile\.in$ ^INSTALL$ ^aclocal\.m4$ ^build-.*($|/) ^configure$ ^autom4te\.cache($|/) ^config\.in\.h$ # e.g. doc/faq/OctaveFAQ.info # doc/interpreter/octave.info-4 ^doc/.*\.info(-\d)?$ ^doc/\w*/stamp-vti$ ^doc/\w*/version\.texi$ ^doc/interpreter/images\.mk$ # e.g. liboctave/operators/smx-op-inc.mk ^liboctave/operators/\w+-op-\w+\.mk$ ^libinterp/dldfcn/module\.mk$