Changes

Jump to navigation Jump to search
Line 45: Line 45:  
* jwe had a look at Octave own reference counting
 
* jwe had a look at Octave own reference counting
 
* Wish to replace it with C++ shared pointers
 
* Wish to replace it with C++ shared pointers
* Expert knowledge wanted!
+
* Expert knowledge wanted! jwe opened a [https://octave.discourse.group/t/using-std-shared-ptr-t-to-implement-copy-on-write-objects-in-octave/1436 discussion thread]
** jwe will reach out on Discourse about the exact problems.
   
* jwe identified "copy expensive" inefficiency about mxArray to octave_value conversion? (some clarification needed)
 
* jwe identified "copy expensive" inefficiency about mxArray to octave_value conversion? (some clarification needed)
 
** Root of the trouble lies in historical handling of complex data?? (some clarification needed)
 
** Root of the trouble lies in historical handling of complex data?? (some clarification needed)
 +
https://octave.discourse.group/t/using-std-shared-ptr-t-to-implement-copy-on-write-objects-in-octave/1436
    
== Previous topics ==
 
== Previous topics ==

Navigation menu