|
From: | Quentin Spencer |
Subject: | deprecated builtin variables (was Re: Problem with reading lists) |
Date: | Wed, 09 Mar 2005 15:39:18 -0600 |
User-agent: | Mozilla Thunderbird 0.9 (X11/20041127) |
I wrote:
John W. Eaton wrote:Good point. I've gone back and removed all references to eval, and updated the documentation and changelog in the following patch. I tested it on the simple case given in the help text and it seems to work properly. If there are no objections, I'll check the updated version into octave-forge CVS.On 9-Mar-2005, Quentin Spencer <address@hidden> wrote:| I think this patch may be all that is necessary. I've never used | textread--does someone want to test it?Yes, this might be all that is *needed*, but that function would also be a lot better if it avoided the use of eval. I don't see why it is necessasry to use eval to create return values with the names a1, a2, ..., aN, and then use eval again to assign the temporary variables to varargout{1}, varargout{2}, ..., varargout{N}. It seems it should be possbile to do that in one step, without eval.
OK, looking at my updated code again, I see that there are references to three builtin variables that may no longer be relevant: empty_list_elements_ok, warn_empty_list_elements, and prefer_column_vectors. The only one of these three that octave 2.1.67 recognizes is warn_empty_list_elements. Have the others been removed/deprecated?
-Quentin ------------------------------------------------------------- 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 -------------------------------------------------------------
[Prev in Thread] | Current Thread | [Next in Thread] |