Recent updates to I/O package xmlread API leave Matlab/Octave incompatible

[Pablo Mayrgundter]

Hi All,

First off, thanks for doing Octave dev work!  I just came across what I
think is a recent Octave/Matlab incompatibility that I wanted to notify you
about.

I just grabbed the io package from octave-forge and tried to use it to load
some OSM data using the OSM Fuctions Matlab package:

 
http://www.mathworks.com/matlabcentral/fileexchange/35819-openstreetmap-functions

But it failed, as the xmlread function in the current octave-forge package
only loads a custom format XML that defines internal octave datatypes.  This
looks to be a recent update by carandraug:

 
http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/main/io/src/xmltree_read.l?revision=10145&view=markup

(search for "Bad declaration" to see that it's expecting an octave.dtd
declaration, and will fail on generic XML)

Matlab's xmlread function, on the other hand, works for abritrary XML, by
returning a DOM tree:

  http://www.mathworks.com/help/techdoc/ref/xmlread.html

Is this API divergence intentional?  It seems to me Octave's xmlread should
behave like Matlab's, and the custom octave-xml code that's in there now
should be moved to different naming, like octaveXmlRead or something.

Cheers,
Pablo


--
View this message in context: 
http://octave.1599824.n4.nabble.com/Recent-updates-to-I-O-package-xmlread-API-leave-Matlab-Octave-incompatible-tp4532969p4532969.html
Sent from the Octave - General mailing list archive at Nabble.com.