Editing Online Developer Meeting (2021-11-23)

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 54: Line 54:
 
** Idea: static_cast vs. dynamic_cast: patch {{patch|10139}}
 
** Idea: static_cast vs. dynamic_cast: patch {{patch|10139}}
 
** General remark: Prefer standard features instead of "reinventing the wheel" by implementing intricate optimizations.
 
** General remark: Prefer standard features instead of "reinventing the wheel" by implementing intricate optimizations.
 
== Previous topics ==
 
:''The following items were not discussed.  Just some links to progress on those items are displayed.''
 
 
=== Progress of Octave 6.4.0 release ===
 
 
[https://octave.discourse.group/t/start-release-process-for-octave-6-4-0/1652 Start release process for Octave 6.4.0]
 
 
* State of OpenBLAS compilation bug(?): [https://savannah.gnu.org/bugs/index.php?61246 bug #61246: matrix inversions give wrong results (inv, lu, mldivide)]
 
** Ask for testing the release candidate (Markus)
 
* <code>pkg test sparsersb</code> crashes Octave (only when installed to read-only directory?).
 
** Needs further investigation. See [https://savannah.gnu.org/bugs/index.php?61393 bug #61393].
 
* Which version numbers to update in which files on (minor) release? (CITATION file?)
 
** jwe will add rules for an automatic update.
 
* Update of merge date for Octave 7.x?
 
** Probably early November?
 
 
=== Importance of allowing Octave headers in C language sources ===
 
 
Some header files in Octave have been written to allow them to be compiled by a C compiler.  It is not clear whether anyone really needs to do that and it adds somewhat to the cost of maintaining Octave to ensure that this goal is met, even for just a few of the public header files.  Would it be OK to change Octave so that public header files require a C++ compiler?  And would it be OK to make this change in version 7 without deprecating and preserving the current coding style for two release cycles?
 
 
See bug report [https://savannah.gnu.org/bugs/?61370 bug #61370] and also comments 39 and 40 in [https://octave.discourse.group/t/using-m-prefix-for-member-variables-in-c-classes/1517 this discourse discussion] for some motivating examples of cases where it might be simpler to expect that Octave header files will be compiled by a C++ compiler.
 
 
* Go ahead and remove support for compiling these headers in C. jwe will go through the sources and evaluate uses of <code>#ifdef __cplusplus</code>.
 
 
=== <code>spawn</code> with <code>P_OVERLAY</code> works differently on POSIX and Windows ===
 
 
Markus' current understanding:
 
* <code>spawn</code> with <code>P_OVERLAY</code> replaces the current process with a new one. On POSIX, another process waiting for the original process (like a terminal) will wait for the '''replacing''' process instead.
 
* On Windows, <code>spawn</code> with <code>P_OVERLAY</code> also replaces the current process. But each process has a distinct id on Windows. I.e., the new process gets a different process id from the original one. Another process (like a terminal) waiting for the original process id will resume once the '''original''' process terminates. (The same happens with <code>exec</code>.) That leads to issues when trying to use the <code>octave.exe</code> wrapper on Windows.
 
* Could we use <code>spawn</code> with <code>P_WAIT</code> instead? IIUC, that would require passing the return code from the spawned process. What else?
 
** '''[jwe]''' We have too many different ways of starting and interacting with subprocesses (popen, popen2, system, spawn, procbuf, procstream, etc.).  Is it possible to use just one C++ function to provide all the public functions we need to support?
 
*** '''[mmuetzel]''' Afaict, there is currently no standard C++ function that would do that. Maybe <code>std::process</code> could fill that gap once/if it makes it into the standard (maybe C++23?): [http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1750r1.pdf P1750R1 A Proposal to Add Process Management to the C++ Standard Library]
 
** '''Long term:''' Get rid of the wrapper program on all platforms. That would require the new command line interface and the possibility to dynamically load the GUI (optionally). This will probably not happen before Octave 8.
 
** '''Short term:''' Test if the wrapper can be replaced with a link (or copy) of "octave-gui.exe" in MSYS2. See [https://savannah.gnu.org/bugs/?61396 bug #61396: octave wrapper executable not working properly on Windows]
 
 
=== Octave 7 ===
 
 
In preparation of the next release, start preparing a list of blocking issues (from the bug tracker?).
 
 
* Created [[7.1 Release Checklist]].
 
 
=== Paths with spaces (on Windows) ===
 
 
Background: [https://en.wikipedia.org/wiki/8.3_filename Short file names] are de-activated in more and more Windows systems by default. It is no longer a viable workaround to use them to fix issues with spaces in paths.
 
 
* '''For Octave 7, still install to "Program Files" by default.''' Keep the workaround with conversion to short file names intact for released versions. Remove the conversion to short file names in nightly builds on https://octave.space when the first nightlies of Octave 7 will be built.
 
 
* Try to fix those issues where we find them or get reports.
 
  
 
== See also ==
 
== See also ==

Please note that all contributions to Octave may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Octave:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Templates used on this page: