Latest revision |
Your text |
Line 15: |
Line 15: |
| ** Crash to desktop fixed in librsb ([https://savannah.gnu.org/bugs/?60042 bug #60042], only affects Windows bundle). | | ** Crash to desktop fixed in librsb ([https://savannah.gnu.org/bugs/?60042 bug #60042], only affects Windows bundle). |
| ** Command line arguments with parameters (e.g. <code>--path</code>) can't be combined with <code>--gui</code> ([https://savannah.gnu.org/bugs/?60886 bug #60886]). | | ** Command line arguments with parameters (e.g. <code>--path</code>) can't be combined with <code>--gui</code> ([https://savannah.gnu.org/bugs/?60886 bug #60886]). |
|
| |
| * Ask on discourse for pending changes and do a new release.
| |
|
| |
|
| === Approximate release date for Octave 7? === | | === Approximate release date for Octave 7? === |
Line 25: |
Line 23: |
| ** 4.4.x: merge to stable: 2018-04-04 --- release: 2018-04-30 (< 1 month) | | ** 4.4.x: merge to stable: 2018-04-04 --- release: 2018-04-30 (< 1 month) |
| ** 4.2.x: merge to stable: 2016-09-28 --- release: 2016-11-13 (~ 1.5 month) | | ** 4.2.x: merge to stable: 2016-09-28 --- release: 2016-11-13 (~ 1.5 month) |
|
| |
| * Unfinished projects:
| |
| ** Symbol visibility breaks tests for indexing expressions on macOS. Also many linker warnings similar to this (see [https://savannah.gnu.org/bugs/index.php?59820 bug #59820]):
| |
| ld: warning: direct access in function 'conv_to_int_array(Array<octave::idx_vector> const&)' from file 'liboctave/array/.libs/libarray.a(libarray_la-Array-util.o)' to global weak symbol 'vtable for Array<long long>' from file 'liboctave/array/.libs/libarray.a(libarray_la-Array-i.o)' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings.
| |
| ** Support paths including spaces (mostly for Windows - '''not''' relying on short file names). What about package Makefiles? Probably best if we defer that one to later.
| |
| ** more efficient mex file interface with direct pointers to data in Octave arrays (jwe)
| |
| ** Prefer OCTAVE_LOCAL_BUFFER over Array objects where possible (Rik, not a blocker)
| |
|
| |
| * Probably merge default to stable some time in November
| |
| * Probably release Octave 7 around the end of this year or early 2022.
| |
|
| |
|
| === CamelCase in Octave functions? === | | === CamelCase in Octave functions? === |
|
| |
|
| * What is our current stance on that? --> Avoid it for consistency. Allowed for compatibility. | | * What is our current stance on that? |
| | |
| === Octave released on MSYS2 ===
| |
| | |
| * Not aiming to replace MXE Octave (more reliable, tested, stable(?)). Rather complement it.
| |
| * Target group:
| |
| ** Users that want to use e.g. Octave packages that depends on third party packages not included in MXE Octave.
| |
| ** Users that need features of newer versions of packages that are included in MXE Octave.
| |
| | |
| === GCC plugins ===
| |
| | |
| * Call out to anyone who has experience with compiler plugins
| |
| * Is it possible to write a compiler plugin that identifies variables that match certain conditions? E.g., <code>m_</code> prefix for member variables.
| |
| * Might allow other analysis of the code: E.g., are static or global variables used in a thread-safe manner?
| |
| | |
| === Convenience function to check for integer property ===
| |
| | |
| * Add a function that checks if a double has an integer value.
| |
| * Also return true for integer type input.
| |
| * What is a good name (in Octave and C++ code)?
| |
| | |
| === Broadcasting with special matrix types ===
| |
|
| |
|
| * Topic comes up repeatedly in bug reports.
| |
| * Add convenience option to disable support for these types (range, diagonal matrix, permutation matrix)?
| |
| * Cast to full matrices before broadcasting? Special handling for NaN and Inf values!
| |
|
| |
|
| == Previous topics == | | == Previous topics == |