Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command Line arguments refactor #49

luserx0 opened this issue Aug 25, 2019 · 1 comment


Copy link

commented Aug 25, 2019

Currently, BMX7 uses the ODI interface (as can be seen here), with which per every single file of .c code near the end we find the options handling.

To me this seems overly complicated for two reasons:

  1. The command line argument options stretch out and around all of bmx7's code base which makes difficult to administer
  2. There is no conformity among the options and/or instructions on how to add/remove them

On the other hand, with this approach every single option can be covered in a single line at a specific place and the handling of hierarchy among options is automagically taken care of.

@axn Do you have any ideas on how to begin simplifying options bit by bit?

Another aspect of the command line options is that they are complicated for a simple user. I'm not sure how much of a super user a bmx7 node administrator or user must be, but we should definitely have two modus operandi. One on auto-pilot and one on god-mode.

@aparcar Suggestions on what can be automated?


This comment has been minimized.

Copy link

commented Sep 3, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.