Re: compiling .m files

[Mike Miller]

On Tue, 12 Nov 2002, A S Hodel wrote:

> An octave m-file compiler is one of the wish-list items out there, along
> with a block-diagram simulation tool, symbolic math (some work done here
> I think), etc.


I'm not quite clear on the original question.  I believe that Octave, like
MATLAB, compiles .m functions in memory the first time they are executed.
The 'whos' command shows a list of compiled functions...

octave:1> var(rand(4));
octave:2> whos

*** currently compiled functions:

prot  type               rows   cols  name
====  ====               ====   ====  ====
 wd   user function         -      -  var


If the question was about making a binary executable from an .m file so
that the executable can be called from the command line, I assume we don't
have that.  I don't know how much faster it would be for large, time-
consuming jobs than writing an octave script that can be called from the
command line, compiling the needed .m files in memory and executing them
within Octave.  Certainly, unless the binary executable is to call Octave
to get it's work done, it will usually need to have a lot of Octave
compiled into it, no?

Regards,

Mike



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------