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.
This is probably THE critical thing for me to even think about "formally" releasing v0.1 of reaverlib.
configurationmust be throughoutly refactored, especially in parts that touchboost::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.
boost::program_optionswrapperboost::program_optionswrapper tutorial