List view
Each object in a parser needs a proper help message. I intend for this to be as customizable as possible, without users having to reprogram the entire package. There are several ways to achieve this, but I want this to be done in a modularized manner, such that it is simple to change the way help messages are formatted as standard, while also giving a simple way for customizing the help message for a single argument. As a near-unthinkable example one might wish to be able to include a matrix argument input, with the standard help message being > -m vectors seperated by comma, each specifying the row of a matrix, for example [1, 2, 3, 4],[5, 6, 7, 8] would be a 2x4 matrix. but one could also provide this as a file, and for this it could be o interest to provide an example of this file, eg. > -m A file containing a matrix, columns seperated by comma and rows seperated by a newline. The matrix below is an example file: > 1,2,3,4 > 5,6,7,8 I would like both of these to be possible.
No due dateA component of any good commandline argument parser is the parser object. In classic functional programming this parser would both contain, parse and return the arguments passed. In this package it is merely meant as a shell for other objects which takes care of parsing the actual arguments. The parser should itself not add non-standard arguments, but it should contain some arguments such as 'help' for setting up the object itself.
No due dateBefore the cmdline.arguments package can be complete each component of the low(ish)-level R6 api needs to be implemented. The base class for containing, parsing and handling arguments is the `arguments` class. This milestone is meant to track the progress of this class, which should be the first to be partially completed.
No due date•1/1 issues closed