John W. Eaton wrote:
> On 11-Jun-2007, Olaf Till wrote:
>
> | So this probably will solve the problem. Still IMHO it is worth
> | considering to make octaves "save" and "load" code work on strings
> | (like octave-xmltools) or, better, on file descriptors (or
> | sockets). It would be more straightforward than producing XML strings
> | with an external tool and feeding them through the pipe by hand.
>
> If you want to discuss a change like this, then please open a thread
> on the maintainers list. A proposed patch would also help...
>
> jwe
>
In fact a change like that wouldn't be too difficult as the prototypes
for octave's binary format
extern bool
save_binary_data (std::ostream& os, const octave_value& tc,
const std::string& name, const std::string& doc,
bool mark_as_global, bool save_as_floats);
extern std::string
read_binary_data (std::istream& is, bool swap,
oct_mach_info::float_format fmt,
const std::string& filename, bool& global,
octave_value& tc, std::string& doc);
would tell you. You just need a wrapper to setup the iostreams on both
sides and then install the variables into memory on the reader's side...
Should be relatively easy..