Laurent Mazet's e-mail address from the copyright notice was invalid.
Resending to the new one as on is private page.

On 5 April 2012 22:37, Carnë Draug <carandraug+...@gmail.com> wrote:
> Hi Pablo
>
> you're using the wrong mailing list, xmlread  is in a package and so
> I'm moving it to octave-forge mailing list. I'm also e-mailing Laurent
> Mazet since he wrote the code in question. I have also edited the
> subject line.
>
> On 4 April 2012 20:32, Pablo Mayrgundter <pablo.mayrgund...@gmail.com> wrote:
>> 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
>
> This commit is nothing else more than moving the functions that were
> previously on the miscellaneous package to the IO package.
>
>> 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.
>
> Yes it should but unfortunately no one has yet coded a compatible
> version. Do you think you could edit the current code to be matlab
> compatible?
>
> On 5 April 2012 02:34, Pablo Mayrgundter <pablo.mayrgund...@gmail.com> wrote:
>> Happy to help, though not sure how involved it is.  I see you're maintaining
>> it, so maybe we can chat through a few patches?
>
> Actually this functions have no maintainer. I have just moved them to
> the IO package for sake of organization but neither me or Philp
> actually wrote them. They have pretty much no documentation whatsoever
> so I added Laurent Mazet (the original author of the code) to the list
> of recipients. I hope his e-mail address is still valid.
>
>> If so, next issue is that when I go to build packages, the Makefile
>> in octave-forge/packages tries to
>> fetch http://octave.sourceforge.net/packages.md5 which is 404.  It looks
>> fairly important for the build versioning process.. any suggestion of how to
>> proceed?
>
> This is no issue. That part of the repository is old, very old. Don't
> look into it. You should be looking into octave-forge/main/io/
>
> Carnë

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev

Reply via email to