Online Developer Meeting (2024-01-23): Difference between revisions

Jump to navigation Jump to search
Line 4: Line 4:
== Today's topics ==
== Today's topics ==
* Enable polymorphic-allocators by default? In Octave 9? In Octave 10? Later? See [https://octave.discourse.group/t/enable-polymorphic-allocator-by-default-if-available/5132 Enable polymorphic allocator by default (if available)?] '''Leave it disabled by default on Octave 9. Enable it by default for Octave 10. Test in the next year, notify in NEWS that it will require a C++17 compiler so that packages can update their flags.'''
* Enable polymorphic-allocators by default? In Octave 9? In Octave 10? Later? See [https://octave.discourse.group/t/enable-polymorphic-allocator-by-default-if-available/5132 Enable polymorphic allocator by default (if available)?] '''Leave it disabled by default on Octave 9. Enable it by default for Octave 10. Test in the next year, notify in NEWS that it will require a C++17 compiler so that packages can update their flags.'''
* Disable visibility flags by default for Octave 9?
* Disable visibility flags by default for Octave 9? '''Yes, disable visibility flags for Octave 9, meaning export all symbols by default. Make necessary refactoring on default branch for Octave 10. Maybe examine whether templates and classes should be refactored as well.'''
* Release candidate for Octave 9? Any pending changes still missing for the RC?
* Release candidate for Octave 9? Any pending changes still missing for the RC?
* Blocking tasks before moving any classdef-based class (e.g., string, table, datetime, ...) into Octave core?
* Blocking tasks before moving any classdef-based class (e.g., string, table, datetime, ...) into Octave core?
179

edits

Navigation menu