[Top][All Lists]

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

Re: execution speed in *oct files

From: Tomislav Goles
Subject: Re: execution speed in *oct files
Date: 07 Jun 1999 14:15:16 -0400

/ Artur Jorge Azevedo Carvalho <address@hidden> wrote:
> Hi all,
> I've found that this may be a topic worth of discussion, so if you all don't
> mind i'd
> like to share my thoughts on this...
> I'd like to start on pointing that octave, i should say the core of octave,
> has reached a
> rather stable point, i think, in terms of basic structures which octave is
> based on, and
> no question about it, it has proved as beiing a usefull tool for all of us.
> Now, of course the PROJECTS file is rather long, and things such as sparse
> matrices,
> multidimensional arrays, etc are always important improvements. But isn't
> speed also
> important? Isn't this the reason of being of .oct files? So, in the users
> perspective what
> is at this point more important? Wouldn't be important to make Octave faster
> before
> turning it more and more dependant on its actual structure?
> ...

I think you have a good point about the speed issue. I have found that
due to particularly this issue I usually end up using octave for
prototyping and once I finally go into production I end up re-writing
most of the app to C/C++. However, i'm not sure changing the existing
octave c++ code is the way to go. It may be better to use blitz++
(which is GPL) or something similar instead as the underlying c++ code.
Of course this is probably a very long time ahead solution as it would
involve a major re-design of most of octave.
Tomislav Goles

Octave is freely available under the terms of the GNU GPL.  To ensure
that development continues, see
Instructions for unsubscribing:

reply via email to

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