Editing Online Developer Meeting (2021-09-28)
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
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]). | ||
=== Approximate release date for Octave 7? === | === Approximate release date for Octave 7? === | ||
Line 27: | Line 25: | ||
* Unfinished projects: | * Unfinished projects: | ||
** Symbol visibility breaks tests for indexing expressions on macOS. Also many linker warnings similar to this | ** Symbol visibility breaks tests for indexing expressions on macOS. Also many linker warnings similar to this: | ||
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. | 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. | ** 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. | ||
** | ** others? | ||
=== CamelCase in Octave functions? === | === CamelCase in Octave functions? === | ||
* What is our current stance on that? | * What is our current stance on that? | ||
=== Octave released on MSYS2 === | === Octave released on MSYS2 === | ||
Line 46: | Line 40: | ||
** Users that want to use e.g. Octave packages that depends on third party packages not included in MXE Octave. | ** 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. | ** Users that need features of newer versions of packages that are included in MXE Octave. | ||
== Previous topics == | == Previous topics == |