Online Developer Meeting (2025-07-01): Difference between revisions
Jump to navigation
Jump to search
(Add question about MXE Octave) |
m (Add new topics) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
== Today's topics == | == Today's topics == | ||
* Reorganization of liboctave (place GNU Readline in libinterp?) | * Reorganization of liboctave (place GNU Readline in libinterp?) '''Rik will investigate how difficult this is''' | ||
* Naming conventions in liboctave & libinterp for duplicate names (Has been '''lo-'''). | * Naming conventions in liboctave & libinterp for duplicate names (Has been '''lo-'''). | ||
* Naming conventions in libinterp (Should we use a prefix such as '''pt-''', '''ov-''', '''ls-''' to indicate which block a piece of code belongs too? If so, why isn't every file in parse-tree labeled with '''pt-'''? | * Naming conventions in libinterp (Should we use a prefix such as '''pt-''', '''ov-''', '''ls-''' to indicate which block a piece of code belongs too? If so, why isn't every file in parse-tree labeled with '''pt-'''? | ||
* Capitalization of file names? Why is it '''Cell.h''', not '''cell.h'''? Other examples, '''Quad.h''', '''DASPK.h''' | * Capitalization of file names? Why is it '''Cell.h''', not '''cell.h'''? Other examples, '''Quad.h''', '''DASPK.h'''. ('''Probably too hard because of case-insensitive file systems.''') | ||
* Replace the abundant files in `liboctave/operators/` with modern C++ templates? | |||
* Update binutils in Octave for Windows from 2.40 to 2.44 on the release branch of MXE Octave now? | * Update binutils in Octave for Windows from 2.40 to 2.44 on the release branch of MXE Octave now? | ||
* Should we discontinue NA? | |||
== Previous topics == | == Previous topics == | ||
Latest revision as of 19:25, 1 July 2025
- Date: Tuesday, July 1, 2025 @ 18:00 UTC Convert timezones here!
- Location: https://meet.jit.si/octave-dev
Today's topics
- Reorganization of liboctave (place GNU Readline in libinterp?) Rik will investigate how difficult this is
- Naming conventions in liboctave & libinterp for duplicate names (Has been lo-).
- Naming conventions in libinterp (Should we use a prefix such as pt-, ov-, ls- to indicate which block a piece of code belongs too? If so, why isn't every file in parse-tree labeled with pt-?
- Capitalization of file names? Why is it Cell.h, not cell.h? Other examples, Quad.h, DASPK.h. (Probably too hard because of case-insensitive file systems.)
- Replace the abundant files in `liboctave/operators/` with modern C++ templates?
- Update binutils in Octave for Windows from 2.40 to 2.44 on the release branch of MXE Octave now?
- Should we discontinue NA?
Previous topics
- Release of Octave 10.2.0 DONE
- Octave packages and sourceforge?
See also
- Next meeting: Online Developer Meeting (2025-07-22)
- Prev meeting: Online Developer Meeting (2025-05-27)