1,847
edits
Online Developer Meeting (2021-03-23): Difference between revisions
Jump to navigation
Jump to search
→See also: Announce next meeting.
(→See also: Announce next meeting.) |
|||
| (6 intermediate revisions by one other user not shown) | |||
| Line 43: | Line 43: | ||
* Unify widget for all OSes | * Unify widget for all OSes | ||
* Make jwe's patch a configurable options for testing (nothing to use productively yet) | * Make jwe's patch a configurable options for testing (nothing to use productively yet) | ||
* Need to implement own pager (scroll bar) | * Need to implement own pager (alternatively: scroll bar only) | ||
* Better responsibility delegation between GUI and interpreter | * Better responsibility delegation between GUI and interpreter | ||
** Big matrix output: interpreter | ** Big matrix output: interpreter could ask GUI to print big matrix, GUI could confirm with user, etc. | ||
** Formatting (colors, URLs, etc.) | ** Formatting (colors, URLs, etc.) could be done by the GUI. Interpreter does not need to know about window-width, etc. | ||
===== | ===== Backend code improvements ===== | ||
* "Ditch" old UNIX system functions (e.g. popen) | * "Ditch" old UNIX system functions (e.g. popen) | ||
** Move to package? | ** Move to package? | ||
* | ** compose a list of functions that are candidates for removal from core Octave. See: [https://octave.discourse.group/t/moving-posix-system-call-and-library-functions-out-of-core-octave/1027 Moving POSIX system call and library functions out of core Octave] | ||
** use <code>std::unordered_map</code>, rather than <code>std::map</code> to increase interpreter lookups | * performance of symbol lookup | ||
** symbol | ** use <code>std::unordered_map</code>, rather than <code>std::map</code> to increase performance (e.g. of interpreter lookups) | ||
* | ** Potentially implement "import" keyword? That would probably slow down symbol lookup some more. | ||
* favor C++ std-library functions over gnulib | * Replace custom reference counters with implementation using <code>std::shared_ptr</code> | ||
** Some instances are more difficult to replace. jwe will post something about this on the discourse forum. | |||
* favor C++ std-library functions over gnulib where possible | |||
** Maybe require C++14 or C++17? See: [https://octave.discourse.group/t/using-c-17-features/1026 Using C++17 features] | |||
* improve HDF5 integration | * improve HDF5 integration | ||
** Key to support latest Matlab file formats. | ** Add "wrapper" for libhdf5 functions in Octave's scripting language. | ||
** Key to support latest Matlab file formats. Try to implement in the interfaces for that format in .m file functions. | |||
** Some developers very interested in this! | ** Some developers very interested in this! | ||
| Line 86: | Line 90: | ||
* Automatically reschedule the meeting monthly (Kai suggests on Discourse) | * Automatically reschedule the meeting monthly (Kai suggests on Discourse) | ||
* MXE Octave branches and buildbots | |||
* Strategy for transition to string class syntax (incompatible to current double-quoted character vectors in Octave)? | |||
* Allow using more modern C++ dialects (C++17 STL std::filesystem or boost::filesystem)? | |||
== See also == | == See also == | ||
* Next meeting: | * Next meeting: [[Online Developer Meeting (2021-04-27)]] | ||
* Last meeting: [[Online Developer Meeting (2020-11-10)]] | * Last meeting: [[Online Developer Meeting (2020-11-10)]] | ||
[[Category:2021]] | [[Category:2021]] | ||
[[Category:Meetings]] | [[Category:Meetings]] | ||