1,207
edits
Online Developer Meeting (2025-08-26): Difference between revisions
Jump to navigation
Jump to search
m
Online Developer Meeting (2025-08-26) (view source)
Revision as of 14:07, 26 August 2025
, 26 AugustAdd new topics
m (Add new topics) |
m (Add new topics) |
||
| Line 6: | Line 6: | ||
* Prepare release of Octave 10.3.0? 33 "actual" changes on the stable branch since the release of Octave 10.2.0 (ignoring, e.g., changes to the CI rules or reverted changes), 7 of which are documentation only. | * Prepare release of Octave 10.3.0? 33 "actual" changes on the stable branch since the release of Octave 10.2.0 (ignoring, e.g., changes to the CI rules or reverted changes), 7 of which are documentation only. | ||
** Any pending changes or bugs that need to be fixed for the stable branch? | ** Any pending changes or bugs that need to be fixed for the stable branch? | ||
bug #67459 (clear ?) | |||
* Should Octave be built without debugging code for parser by default? | * Should Octave be built without debugging code for parser by default? | ||
The debugging code is always there and always enabled. For every statement parsed there is a check on the the parse_debug_flag to see whether debugging information should be printed. But, this is really infrequently used code. I have turned on the debugger in the parser just once in 10 years. To me, this is specialist code that could be enabled by a developer during configuration or with a `-D` option to `cpp`, but ordinary users will never need this. | The debugging code is always there and always enabled. For every statement parsed there is a check on the the parse_debug_flag to see whether debugging information should be printed. But, this is really infrequently used code. I have turned on the debugger in the parser just once in 10 years. To me, this is specialist code that could be enabled by a developer during configuration or with a `-D` option to `cpp`, but ordinary users will never need this. | ||