[Octave-bug-tracker] [bug #59847] Unexpected behavior of evalin in some cases

[John W. Eaton]

Follow-up Comment #10, bug #59847 (project octave):

Maybe a possible temporary way to avoid the API change would be to have each
create function ask the call stack for the current frame.  But that means that
each time a new frame is pushed on the call stack.  One way would be to add


  call_stack& cs = __get_call_stack__ ("...");
  m_caller = cs.current_frame ();


in the stack_frame constructor.  Or, since there can currently be only one
interpreter/evaluator/call stack object, we could probably cache the
call_stack object in a static variable the stack_frame class.

Or we could just break backward binary compatibility for this release.

Thoughts?


    _______________________________________________________

Reply to this item at:

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

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