[Top][All Lists]

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

Re: gnuplot_binary in 2.9.6+

From: Dmitri A. Sergatskov
Subject: Re: gnuplot_binary in 2.9.6+
Date: Tue, 25 Jul 2006 08:38:14 -0600

On 7/25/06, John W. Eaton <address@hidden> wrote:
On 24-Jul-2006, Dmitri A. Sergatskov wrote:

| I assume that gnuplot_binary is no more in 2.9.6 and beyond.
| So, how do I go about telling octave to use a different
| (gnuplot or not) plotter?

Please read the NEWS file.  It explains that all built-in variables
have been converted to functions.  So instead of

  gnuplot_binary = "/some/dir/gnuplot";

you need to write

  gnuplot_binary ("/some/dir/gnuplot");

To prevent this kind of question from being the number one topic on
the mailing lists after 3.0 is released, I think I have a way to issue
a warning when assigning to a local variable that used to be built-in.
After sufficient time has passed, I would expect to be able to remove
the warning.

I am sorry I was not very specific. I tried what you have said,
but it did not work:

octave:1> gnuplot_binary("/usr/bin/gnuplot")
error: invalid vector index = 117
octave:1> gnuplot_binary("/home/dima/bin/mygnuplot")
error: invalid vector index = 121

So I assumed it is not a universal conversion, but case-by-case



reply via email to

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