1,847
edits
Short projects: Difference between revisions
Small changes.
(→Review or create changesets: Add pointers how to do it.) |
(Small changes.) |
||
| Line 24: | Line 24: | ||
Implement missing Octave functions or implement desired features and general improvements. | Implement missing Octave functions or implement desired features and general improvements. | ||
* {{bug|32088}} - <code>-ALL</code> option for {{manual|which}} | |||
* {{bug|40211}} - More compact output for structs and cell arrays | |||
* {{bug|41530}} - Editor debug mode could show a dbup/dbdown GUI component | |||
* {{bug|41796}} - extend sub2ind and ind2sub | |||
* {{bug|41844}} - GUI Debug Menu could offer "Stop If..." | * {{bug|41844}} - GUI Debug Menu could offer "Stop If..." | ||
* {{bug|47239}} - calling system without shell | * {{bug|47239}} - calling system without shell | ||
* Lists of missing functions for [[:Category:Missing functions|several packages]]. | * Lists of missing functions for [[:Category:Missing functions|several packages]]. | ||
| Line 55: | Line 56: | ||
== Miscellaneous == | == Miscellaneous == | ||
* C++ cleanup of packages after the switch to exceptions (late 2015).See [[Invert if/else/error]]. | * C++ cleanup of packages after the switch to exceptions (late 2015). See [[Invert if/else/error]]. | ||
* Use "units.h" from [http://www.gnu.org/software/units/ GNU units] in [http://octave.sourceforge.net/miscellaneous/function/units.html function units] (from the Octave-Forge [http://octave.sourceforge.net/miscellaneous/ miscellaneous package]) rather than making a system call and parsing its output (and having to handle multiple versions of it). This change will make it much more robust. It likely will alleviate the requirement of having [http://www.gnu.org/software/units/ GNU units] installed in the system separately by the user. This requires knowledge of C (units is written on C) and C++ to write its Octave interface. It can be very easy if the units.h truly allows to be used as library or maybe impossible if it does not. This has not been investigated yet. | * Use "units.h" from [http://www.gnu.org/software/units/ GNU units] in [http://octave.sourceforge.net/miscellaneous/function/units.html function units] (from the Octave-Forge [http://octave.sourceforge.net/miscellaneous/ miscellaneous package]) rather than making a system call and parsing its output (and having to handle multiple versions of it). This change will make it much more robust. It likely will alleviate the requirement of having [http://www.gnu.org/software/units/ GNU units] installed in the system separately by the user. This requires knowledge of C (units is written on C) and C++ to write its Octave interface. It can be very easy if the units.h truly allows to be used as library or maybe impossible if it does not. This has not been investigated yet. | ||
| Line 61: | Line 62: | ||
* Use non-empty identifiers in all warnings and errors issued by Octave; see {{bug|39439}}, {{bug|39434}}. You may tackle as many or as few IDs as you have time for. As it is a widespread issue, finding occurrences in the source code should give you valuable knowledge about the way Octave files are organized. | * Use non-empty identifiers in all warnings and errors issued by Octave; see {{bug|39439}}, {{bug|39434}}. You may tackle as many or as few IDs as you have time for. As it is a widespread issue, finding occurrences in the source code should give you valuable knowledge about the way Octave files are organized. | ||
** When raising errors and warnings try to use the ids that are documented in the functions [http://octave.sourceforge.net/octave/function/warning_ids.html warning_ids] and [http://octave.sourceforge.net/octave/function/error_ids.html error_ids]. If you really need a new id (please, first read the ones already there!), please add it to those functions as well. If you see other ids used in core that are not given by the functions mentioned above, please, report or submit patch for them, in addition to the patch to the calling functions as well. | ** When raising errors and warnings try to use the ids that are documented in the functions [http://octave.sourceforge.net/octave/function/warning_ids.html warning_ids] and [http://octave.sourceforge.net/octave/function/error_ids.html error_ids]. If you really need a new id (please, first read the ones already there!), please add it to those functions as well. If you see other ids used in core that are not given by the functions mentioned above, please, report or submit patch for them, in addition to the patch to the calling functions as well. | ||
[[Category:Development]] | [[Category:Development]] | ||
[[Category:Project Ideas]] | [[Category:Project Ideas]] | ||
[[Category:Missing functions]] | [[Category:Missing functions]] | ||