Skip to content

configuration: refactor and documentation. #28

@griwes

Description

@griwes

This is probably THE critical thing for me to even think about "formally" releasing v0.1 of reaverlib. configuration must be throughoutly refactored, especially in parts that touch boost::program_options, because the current code is an utter mess. I don't exactly have an idea for this, but I guess that once I start working with this, it should become pretty clear what needs changing and what can stay.

And documentation must be written.

  • refactor of core functionality
  • refactor of boost::program_options wrapper
  • API reference
  • tutorial
  • boost::program_options wrapper tutorial

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions