Editing Online Developer Meeting (2021-04-27)

Jump to navigation Jump to search
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 publish the changes below to finish undoing the edit.

Latest revision Your text
Line 15: Line 15:
* Which branch should the buildbots use?
* Which branch should the buildbots use?
** http://buildbot.octave.org:8010/ (jwe)
** http://buildbot.octave.org:8010/ (jwe)
*** Probably add builders to jwe's buildbot that build the current Octave stable branch with MXE Octave's release branch.
*** Not really sure about a definite decision
*** Is there a way to trigger daily builds of the mxe builders only if there have been changes in Octave or MXE Octave.
** https://buildbot.octave.space/ (Kai)
** https://buildbot.octave.space/ (Kai)
*** General move to "release" branch (probably May)
*** General move to "release" branch (probably May)
Line 25: Line 24:
* Find out how to trigger a build on changes in two repositories?
* Find out how to trigger a build on changes in two repositories?
** Untested idea: https://github.com/gnu-octave/octave-buildbot/pull/9/files
** Untested idea: https://github.com/gnu-octave/octave-buildbot/pull/9/files
=== GitHub ===
* Markus wants to try out using GitHub runners
** https://octave.discourse.group/t/ci-with-github-hosted-runners/1081
** Try out macOS runners
* Therefore a folder ".github" will be added to the Octave main repo
** Can be removed anytime if it proves as not useful.
* If other services (despite GitHub) are going to be tested, respective files might be added too.


=== String class strategy ===
=== String class strategy ===


* Strategy for transition to string class syntax (incompatible to current double-quoted character vectors in Octave)?
* Strategy for transition to string class syntax (incompatible to current double-quoted character vectors in Octave)?
** Issue treatment of escape characters (first interpreted when Xprintf is applied).
*** https://www.mathworks.com/help/matlab/ref/string.html
* Suggestion to implement an initial string class at one point
** Many existing Octave code (packages) might break.
** In the transition time using
*** Octave .oct-config files to manage how double quoted strings are treated
*** Implement convertStringsToChars and solve issue per function basis (Matlab compatible, probably straight forward, but many changes).
**** https://www.mathworks.com/help/matlab/ref/convertstringstochars.html
* Initial implementation by Andrew Janke
** https://github.com/apjanke/octave-tablicious/blob/master/inst/string.m
** http://blog.apjanke.net/2019/04/20/matlab-string-representation-is-a-mess.html
=== Classdef ===
* Wish to define classdef classes from C++ "nicely" (currently only from m-files comfortable usable).
* This would also help implementing the string class.


=== C++17 ===
=== C++17 ===
Line 59: Line 33:
* Updates: https://octave.discourse.group/t/using-c-17-features/1026
* Updates: https://octave.discourse.group/t/using-c-17-features/1026
* Allow using more modern C++ dialects (C++17 STL std::filesystem or boost::filesystem)?
* Allow using more modern C++ dialects (C++17 STL std::filesystem or boost::filesystem)?
** qt6 requires C++17 https://www.qt.io/blog/qt-6.0-released
** gcc 8.x (2018) still not C++17 feature complete (e.g. std::filesystem cannot fully be used, no benefit)
*** https://en.cppreference.com/w/cpp/compiler_support#cpp17
*** https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2017
General consensus was to stay with C++11 until a "killer application" shows up that rectifies changing to a newer standard.


=== Short introduction: SavannahAPI ===
=== Short introduction: SavannahAPI ===
Line 95: Line 63:


== Previous topics ==
== Previous topics ==
:''The following items were not discussed.  Just some links to progress on those items are displayed.''


=== Octave 7 ===
=== Octave 7 ===
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)

Template used on this page:

Retrieved from "https://wiki.octave.org/Online_Developer_Meeting_(2021-04-27)"