You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
8000
Many tools process their command-line options in the order they were given, allowing later options to override earlier ones. ESBMC has a different approach of allowing only certain options (those resulting in a list of parameters) to be given mutliple times. For instance, --default-solver X --default-solver Y will result in
ERROR: option '--default-solver' cannot be specified more than once
which seems unintuitive, in particular when combined with the way processing the ESBMC_OPTS environment variable works: by first processing options there, and then those from the command-line. This makes
export ESBMC_OPTS="--default-solver X"
esbmc --default-solver Y
fail without an easy way to determine why.
I'm starting this poll to find out whether there would be interest in allowing non-list options (i.e., normal settings) to be overridden by later ones. Note, this is not restricted to --default-solver, it concerns all options that don't result in an ordered list.
Should ESBMC's option processing be changed to be more in line with Unix command line tools s.t. later options override earlier ones?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Many tools process their command-line options in the order they were given, allowing later options to override earlier ones. ESBMC has a different approach of allowing only certain options (those resulting in a list of parameters) to be given mutliple times. For instance,
--default-solver X --default-solver Ywill result inwhich seems unintuitive, in particular when combined with the way processing the ESBMC_OPTS environment variable works: by first processing options there, and then those from the command-line. This makes
fail without an easy way to determine why.
I'm starting this poll to find out whether there would be interest in allowing non-list options (i.e., normal settings) to be overridden by later ones. Note, this is not restricted to
--default-solver, it concerns all options that don't result in an ordered list.2 votes ·
Beta Was this translation helpful? Give feedback.
All reactions