[Top][All Lists]

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

Re: Very slow reading of a 2D matirx

From: John W. Eaton
Subject: Re: Very slow reading of a 2D matirx
Date: Sat, 22 Oct 2005 19:38:58 -0400

On 22-Oct-2005, Paul Kienzle wrote:

| On Oct 21, 2005, at 8:37 AM, John W. Eaton wrote:
| > On 21-Oct-2005, Paul Kienzle wrote:
| >
| > | If you install the data in the same directory as the script then you
| > | should be able to do:
| > |
| > |   x = load(file_in_loadpath('script_data'))
| >
| > This will usually work, but I think it will fail if the script was
| > invoked with something like
| >
| >   source ("/some/directory/that/is/not/in/the/loadpath/script-file.m");
| >
| > Should Octave export a variable that holds the full name of the
| > current script (or even function) file while it is executing?
| That would be useful in some circumstances, but I wouldn't want every 
| function invocation to be slower just to support it.

I think we already have the variable internally for other purposes.
So if we implement access to it as a function instead of modifying the
value of a variable in the symbol table, I don't think there would be
any penalty unless you request the value.


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

Octave's home on the web:
How to fund new projects:
Subscription information:

reply via email to

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