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

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

[Octave-bug-tracker] [bug #51708] multiple --eval options results in cor


From: Rik
Subject: [Octave-bug-tracker] [bug #51708] multiple --eval options results in corrupted parsing of command line
Date: Wed, 9 Aug 2017 17:07:26 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0

Update of bug #51708 (project octave):

                  Status:                    None => Confirmed              

    _______________________________________________________

Follow-up Comment #2:

Grrr.  I made the change from " " to ' ' to be more specific and because there
were certain cases, such as appending with +=, where it was faster.  And then
I made a second set of changes for readability where I removed the std::string
() qualifying the bare string literal because it was unnecessary.

Again, this points out that we don't have a full set of regression tests
because I ran 'make check' and it passed.

Can we add some invocation tests to the tests/ directory or is it really only
running m-files and .tst files?  For this case,


run-octave --eval "1" --eval "+ 1"


should return 2.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51708>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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