Online Developer Meeting (2024-01-23): Difference between revisions

Jump to navigation Jump to search
 
Line 12: Line 12:
* Blocking tasks before moving any classdef-based class (e.g., string, table, datetime, ...) into Octave core?
* Blocking tasks before moving any classdef-based class (e.g., string, table, datetime, ...) into Octave core?
** '''There is already classdef in Octave core, like inputParser. The difference is that typically there is only one object of inputParser, but Octave core doesn't currently have arrays of classdefs, which would be necessary for arrays of strings etc. See [https://savannah.gnu.org/bugs/?65179] for example'''
** '''There is already classdef in Octave core, like inputParser. The difference is that typically there is only one object of inputParser, but Octave core doesn't currently have arrays of classdefs, which would be necessary for arrays of strings etc. See [https://savannah.gnu.org/bugs/?65179] for example'''
** '''The second major shortcoming is that classdefs cannot currently be saved in files.'''
* Discuss a road map to port @table class from Tablicious package into Octave core, while making it a dependency for Statistics until @table gets into core (possibly by Octave 10).
* Discuss a road map to port @table class from Tablicious package into Octave core, while making it a dependency for Statistics until @table gets into core (possibly by Octave 10).


179

edits

Navigation menu