On 03/12/2021 07:09 AM, [hidden email] wrote:
My vote as well is to just implement this in core Octave. Developer time is limited and spending 1/4-1/3 of the effort setting something up in Octave Forge only to discard it later when the code moves to core seems a grievous waste.
We are also early in the 7.0 cycle so now is the time to make big changes and potentially de-stabilize the code base for a while.
See also this Discourse thread where I introduced some ideas about possible large themes for the next release: https://octave.discourse.group/t/goals-for-the-next-release/358/6.
In particular, two themes I mentioned bear on this discussion:
** strings class (bite the bullet and implement this and, probably, get rid of Octave’s very UNIX-y way of understanding single and double quotes)
** “argument” input validation blocks
** others? Seems like there are tall arrays, dataframes, etc.
** built-in hash operator. I would like to see an O(1) search function incorporated in to the Octave language, similar to hashes in Perl or dictionaries in Python. This would be an extension over what Matlab provides, and could be used to implement containers.Map more easily as well as data frames.
|Free forum by Nabble||Edit this page|