230
edits
Changes
Jump to navigation
Jump to search
Line 45:
Line 45: − + − ** jwe will reach out on Discourse about the exact problems. +
Online Developer Meeting (2021-07-27) (edit)
Revision as of 09:00, 28 July 2021
, 09:00, 28 July 2021→C++ shared pointer / liboctave
* 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 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 ==