[Octave-bug-tracker] [bug #51708] multiple --eval options results in corrupted parsing of command line

[Mike Miller]

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

                 Summary: multiple --eval options results in corrupted parsing
of command line
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Wed 09 Aug 2017 12:41:25 PM PDT
                Category: Interpreter
                Severity: 4 - Important
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

Multiple --eval options should be combined into a single command string to be
evaluated in sequence. This worked in all versions up to the current stable
branch, but looks like it's regressed on the default branch.

Stable:


$ ./run-octave -cli --eval="1+" --eval=1
ans =  2


Default:


$ ./run-octave -cli --eval="1+" --eval=1
parse error:

  invalid left hand side of assignment

>>> 1+E=1
       ^



Depending on the contents of the --eval options, a different string is passed
to the parser. It looks like it's coming from the environment. I think the
environ array normally follows the argv array in memory.




    _______________________________________________________

Reply to this item at:

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

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