help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 'octave' and 'matio'


From: Sergei Steshenko
Subject: Re: 'octave' and 'matio'
Date: Wed, 3 Aug 2011 06:59:01 -0700 (PDT)

--- On Wed, 8/3/11, David Bateman <address@hidden> wrote:

> From: David Bateman <address@hidden>
> Subject: Re: 'octave' and 'matio'
> To: address@hidden
> Date: Wednesday, August 3, 2011, 5:57 AM
> On 08/03/2011 09:43 AM, Jordi
> Gutiérrez Hermoso wrote:
> > Anyways, my question was, we can already read and
> write mat files, are
> > we doing it incorrectly or insufficiently enough to
> warrant throwing
> > out out code or merging it with theirs? What's to be
> gained by this
> > development?
> > 
> 
> 
> Matio can read/write matlab V7.3 files, which are a matlab
> wrapper
> around HDF5. Octave currently can't do that. So this is one
> major reason
> to convert to use matio.
> 
> There's also a residual bug in Octave for zipped matfile's
> that I can't
> seem to fix, see
> 
> http://savannah.gnu.org/bugs/?32167
> 
> that would probably be fixed by using matio.
> 
> However, matio can't treat matlab objects, such as
> anonymous functions
> and so if we convert to matio we'd have to reimplement
> objects.
> 
> D.
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://mailman.cae.wisc.edu/listinfo/help-octave
> 

By the way, to me HDF5 looks horrendously suspicious - one may have a look
at the attached file produced by

grep warning /mnt/sdb8/sergei/AFSWD_debug/build/hdf5-1.8.7/make.log | cut -d: 
-f5 | sort | uniq > hdf5-1.8.7_warnings.txt

command.

Regards,
  Sergei.

Attachment: hdf5-1.8.7_warnings.txt
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]