octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #55023] gnuplot_binary test fails if there's n


From: Carnë Draug
Subject: [Octave-bug-tracker] [bug #55023] gnuplot_binary test fails if there's no gnuplot and leaves incorrect configuration
Date: Wed, 14 Nov 2018 08:15:19 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

URL:
  <https://savannah.gnu.org/bugs/?55023>

                 Summary: gnuplot_binary test fails if there's no gnuplot and
leaves incorrect configuration
                 Project: GNU Octave
            Submitted by: carandraug
            Submitted on: Wed 14 Nov 2018 01:15:17 PM UTC
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

The test for gnuplot_binary changes the internal value of gnuplot_binary to
"__foobar__". If the test fails, then the value is never set back to what it
should.


octave:1> gnuplot_binary 
ans = 
octave:2> test gnuplot_binary 
[...]
!!!!! test failed
gnuplot_binary: NEW_PROG must be a non-empty string
octave:3> gnuplot_binary 
ans = __foobar__


Related to this issue, is the case that an empty string is a valid
gnuplot_binary value (I guess when there's no gnuplot binary on the system),
but setting it as such will fail. I think the check for an empty string should
be removed.




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55023>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

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