[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #46397] eval: The evaluated code should not af
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #46397] eval: The evaluated code should not affect last result |
Date: |
Sat, 2 Sep 2017 08:54:56 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 |
Update of bug #46397 (project octave):
Status: None => Wont Fix
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #2:
I'm marking this as "Won't Fix". It is a Matlab incompatibility, but it also
makes more sense to me to kee it this way. 'eval' runs code that can have
side effects. For example, you can bring new variables into existence with
eval ('x = 2;')
It makes sense to me that a successful evaluation of code is the same as if
the code had been typed, or run from a script, in which case the ans variable
would be updated.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?46397>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #46397] eval: The evaluated code should not affect last result,
Rik <=