[Octave-bug-tracker] [bug #46397] eval: The evaluated code should not affect last result

[Rik]

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/