1,847
edits
Online Developer Meeting (2021-08-24): Difference between revisions
→Todays topics
| Line 6: | Line 6: | ||
* Meet and greet 5 minutes before meeting (audio testing). | * Meet and greet 5 minutes before meeting (audio testing). | ||
=== | === Switch this meeting to more casual format === | ||
* | * In the future notes of the talks will be added to this wiki in a more sparse fashion. | ||
=== | === liboctave === | ||
* | * Make more use of STL | ||
** | * Not all liboctave components can be replaced by STL containers, as the ND-indexing is not supported. | ||
* <code>string_vector</code> class probably replaceable by STL containers. | |||
=== Tips for Octave C++ code writers === | |||
Such as packages, toolboxes, etc. | |||
* Prefer <code>OCTAVE_LOCAL_BUFFER</code> over heavy-weight <code>Array</code> object to store results of (Fortran-) library calls. | |||
* Prefer <code>octave_value</code> type variables over internal data structures. | |||
** Examples: Function handle class and Range class. | |||
=== For package maintainers === | |||
* Do not use <code>error_state</code> anymore! https://octave.discourse.group/t/eliminating-use-of-error-state-in-octave-code/1515 | |||
* Do not suppress compiler warnings about deprecated features today, those are the bug reports of tomorrow, when it is too late. | |||
=== octave namespace === | |||
* jwe made many breaking changes on the default branch moving symbols in the octave namespace, to keep the namespaces tidy. | |||
=== Deprecations === | |||
* The operators <code>.+</code>, <code>.-</code>, and <code>**</code> https://octave.discourse.group/t/deprecating-fortran-style-exponent-operator/1516 will be deprecated. | |||
=== Code sprints === | |||
* Wish for more code sprints, e.g., | |||
** "m_" convention https://octave.discourse.group/t/using-m-prefix-for-member-variables-in-c-classes/1517/17 | |||
** Close easy closable bugs [[Short_projects#Easy_Closes]] | |||
== Previous topics == | == Previous topics == | ||