[Octave-patch-tracker] [patch #8016] Prototype octave_value_list transfer

[Dan Sebald]

Follow-up Comment #10, patch #8016 (project octave):

Maybe.  There were one or two fairly recent discussions on the list about
transferring data back and forth between the GUI and octave core (what's
called a worker thread).

rethinking interpreter <-> gui interaction
[thought there was one in which was examining reference counting]

JWE was revisiting the issue within the past six months.  I don't know where
it stands.  Any patches attached here have probably long been out of date, but
as far as the issue, I think it still exists.

The problem stems from the fact reference counting across the thread to the 
GUI is dangerous (we all had enough experience with reference counting to know
such a scheme would eventually crash) and to make the transfer of data to the
GUI more generic rather than having specific functions to get this data or
that data.  The scheme here moves the data without affecting the atomic
reference count.  (octave_value_list is the most generic form of data in
Octave, it's what all functions return internally.  Thus if the GUI requests a
command, it can get an octave_value_list containing all the results.)

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/patch/?8016>

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