[Top][All Lists]

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

Re: Moving functions from octave-forge to octave

From: Philip Nienhuis
Subject: Re: Moving functions from octave-forge to octave
Date: Thu, 3 Jul 2014 09:06:11 -0700 (PDT)

Ronald wrote
> I read a quote from a 2007 thread of John W. Eaton saying:
> "any function currently in an Octave Forge package that is in
> the list of core Matlab functions is a candidate for moving to
> Octave"
> So I was wondering if the actxserver function from the windows package
> shouldn't be moved to the Octave.
> And what about others like for example xlsread and xlswrite from the io
> package?
> What would be the criteria for moving an Octave Forge function to Octave?

I suppose one of the criteria is that core Octave functions should not be
bound to a specific platform.
Now, actxserver (a sort of "system library") runs only on Windows, so there
you go.

As to xlsread and xlswrite: the way they are coded now is quite involved,
precisely because they should be able to work on about any platform
(currently xlsread/-write can also process gnumeric and ODS). In this way
the Octave versions are much more flexible than their Matlab counterparts;
e.g. AFAIK on Mac OSX or Linux Matlab's xlswrite doesn't work very well, if
it works at all. In that sense, ML is way behind Octave.
The way Octave's spreadsheet functions are offered now, included in an
add-on package, is probably the best solution in the foreseeable future.

What is it you think you will gain with moving them into core Octave?


View this message in context:
Sent from the Octave - General mailing list archive at

reply via email to

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