[Octave-bug-tracker] [bug #45951] Add "xmlread" to core Octave or replace the one in io package

[Philip Nienhuis]

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

@Panxto:
Is it meant for core Octave or for the io package? If it is for core I'll
immediately deprecate io's xmlread/-write/-tree in soon-to-come io-2.2.10. If
for io it can replace its old xmlread right away.
I have no preference here. Your pick?

One thing about the object.method syntax you described that seems to bug me is
that using xerces no "native" Octave objects are obtained (e.g., structs) but
Java objects.
Not such a big deal, but Java objects do have some drawbacks. E.g., they
cannot be saved to file (neither can classdef objects). But I suppose xml doc
objects are destined to be volatile anyway.
On the ML site there is a code example to convert it to structs but obviously
we cannot use that.

Your XML read code might also need a stanza along the lines of:

if (! octave_config_info.features.JAVA)
  error ("xmlread: Octave was built without Java support, exiting");
elseif (! usejava ("jvm"))
  error ("xmlread: no Java JRE or JDK detected, exiting");
endif


+ the try-catch Mike suggested to catch obvious Java problems with some sort
of meaningful error message.

The stanza above could be adapted for any future Java-calling function in
Octave I guess.


In the mean time I also found this:
https://github.com/sbigaret/Euclide/tree/master/utils/octave/xmltoolbox
After this weekend I'll have some bits of time to explore this one. It is 5
years old but also uses xerces (the C++ version I suppose). Hmmm no license
there...

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45951>

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