On Wed, Aug 02, 2017 at 07:29:42AM +, Robert burner Schadek via
Digitalmars-d-announce wrote:
> On Tuesday, 1 August 2017 at 17:46:57 UTC, H. S. Teoh wrote:
[...]
> > There's also UDAs for optionally flattening a nested struct, so that
> > internally I can have separate structs for configuring
On Tuesday, 1 August 2017 at 17:46:57 UTC, H. S. Teoh wrote:
I think UDA-driven configuration parsing is ultimately the
right direction to go. And by that I mean more than just
command-line parsing, but the parsing of configuration
parameters in general, including command-line options,
config
On Tue, Aug 01, 2017 at 03:44:34PM +, Robert burner Schadek via
Digitalmars-d-announce wrote:
> args.d is a command line argument and config file parser.
>
> The basic idea of args.d is that that command line options and config
> file options are basically the same or should be.
> The configu
On Tuesday, 1 August 2017 at 15:44:34 UTC, Robert burner
import args;
I suggest adding a module declaration with some kind of top level
namespace as soon as possible. This is liable to conflict with
some other module with the same name from a user's project.
args.d is a command line argument and config file parser.
The basic idea of args.d is that that command line options and
config file options are basically the same or should be.
The configuration options are build from UDA annotated structs
that can be nested.
The package can be used with dub "
