Online Developer Meeting (2024-01-23)

• Date: Tuesday, Jan 23, 2024 @ 18:00 UTC Convert timezones here!
• Location: https://meet.jit.si/octave-dev

Today's topics

• Enable polymorphic-allocators by default? In Octave 9? In Octave 10? Later? See 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?
• 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?
• Discuss a road map to port @table class from Tablicious package into Octave core, while making it a dependency for Statistics until @table gets into core (possibly by Octave 10).

Previous topics

• Octave 9 remaining release activities
  • Blocking bugs
    • Change in BLAS/LAPACK condition number for `inf (2,2)`. Should we disable tests for this feature to avoid confusion that something is wrong with Octave, while we work on a strategy for this? No.
    • Windows Terminal problems
      • Apparently the Developer option fix may not be readily visible for everyone? see https://octave.discourse.group/t/bug-octave-freezes/5097/9
      • Do we have enough detail to create a useful report upstream at https://github.com/microsoft/terminal/issues ?
  • Translation files
  • First names or abbreviated names in `contributors.in`? Rik will follow up with individuals
  • `-fsanitize` and other checks on code
    • Should leaks be analyzed in Discourse thread or a Savannah bug report? Discourse to start, bug afterwards
  • Approximate date for release candidate

• Octave coding guidelines
  • Need refresh as recommendations are out of date
    • Line length
    • Break return type of function and put on separate line for class methods within class definition? Original reason no longer applies, so use judgment based on e.g. length of return type l
    • `enum`, `struct` style not particularly clear or documented
    • #ifdef indentation and styling No clear preference

• Public roadmap discussion.
  • Example: https://github.com/nelson-lang/nelson/blob/master/ROADMAP.md
  • Example: https://bugs.ruby-lang.org/projects/ruby-master/roadmap
  • OK to create a public roadmap doc based on existing wiki project ideas. Will have target versions but not people.
• Proposal [from cbm]: set aside last 15 or 20 minutes to hack on the bytecode interpreter.
  • JWE asks questions, rest of us file issues or take notes.
  • Example: last meeting something came up about int types...
    • perhaps we can find a few more "low hanging fruit"
  • If nothing else, a few of us will spend a few minutes trying the interpreter.
  • Or could spend time trying to break testing the experimental terminal widget to start generating a buglist
  • Long discussion of code. JWE will try to merge stack frames for tree evaluator and bytecode interpreter. Meeting with Petter planned.

See also

• Next meeting: Online Developer Meeting (2024-02-27)
• Last meeting: Online Developer Meeting (2023-12-19)