216
edits
Online Developer Meeting (2021-10-26): Difference between revisions
Jump to navigation
Jump to search
Online Developer Meeting (2021-10-26) (edit)
Revision as of 19:14, 26 October 2021
, 26 October 2021→Fallback topic: spawn with P_OVERLAY works differently on POSIX and Windows: Update notes from meeting
(→Importance of allowing Octave headers in C language sources: Update from meeting) |
(→Fallback topic: spawn with P_OVERLAY works differently on POSIX and Windows: Update notes from meeting) |
||
| Line 32: | Line 32: | ||
* 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? | * 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? | * [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? | ||
--> 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. | |||
== Previous topics == | == Previous topics == | ||