From octave-sources-request at bevo dot che dot wisc dot edu Tue Aug  7 18:14:52 2001
Subject: Re: load-save
From: Trond Varslot <trond at varslot dot net>
To: hn75 at gmx dot de, octave-sources@bevo.che.wisc.edu
Date: Wed, 08 Aug 2001 09:18:06 +1000

>I am interested in saving structures and while searching the octave 
>mailing lists I found that 1999 Joao Cardoso introduced a patch for 
>ocatve-2.1.12 to tackle this problem.
>http://www.octave.org/mailing-lists/octave-sources/1999/4
>
>After three years it seems that this patch did'nt made it to the 
>unstable version (2.1.*). So Joao made a new against the latest 
>version. You can find it (octave-2.1.34-load-save.cc.patch) here
>http://merlin.inescn.pt/~qual/Octave/octave-2.1.34-load-save.cc.patch
>
>My question is: Why did'nt it get applied to the devel sources? Is is 
>buggy, not good?

This is only related to your question, but perhaps not directly of interest
to you.

I have been working with octave-2.1.33 and 2.1.34 for a while now. I have
saved structures on many an occation without thinking about it. Yesterday
though, I experienced that octave-2.1.34, compiled on a SPARC did not want
to save structures. It made some comment about the struct not being of a
particular type, I don't quite remember the error message:( But this was a
progeam which I have run successfully under octave-2.1.33 and 2.1.34 on an
i686.

I have not compiled octave over again on both platforms to make sure that
the only difference is the architecture, but I am pretty confident it is. I
sure haven't applied any patches to it. When I get my PC back I will
recompile on that to verify my findings 100%.

Does this sound plausible, or have I been having a bad dream?


Yours sincerely
Trond Varslot.
Bloom where you are planted.
http://www.alphalink.com.au/~leda/
http://www.geocities.com/Athens/Ithaca/9286/
http://www.allreaders.com/ProfileView.asp?Name=Janet+Gratton&TopicID=2720