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
{{ message }}
Repository navigation
[FEATURE] Scripts with arguments should use getopts #2631
Is your feature request related to a problem? Please describe.
Manual parsing of arguments makes code harder to read can cause issues like one that is reported here: #2625
Describe the solution you'd like
Use getopts where applicable
changed the title [-][FEATURE] Scripts with arguments should use getopt[/-][+][FEATURE] Scripts with arguments should use getopt/getopts[/+]on Mar 26, 2020
changed the title [-][FEATURE] Scripts with arguments should use getopt/getopts[/-][+][FEATURE] Scripts with arguments should use getopts[/+]on Mar 26, 2020
@crazoes Thanks, I've updated description to use getopts instead of getopt, I think it's better cos it's in posix standard while getopt is not. Are you ok with that?
Activity
crazoes commentedon Mar 26, 2020
@jajanusz @dbaluta I am working on this one.
[-][FEATURE] Scripts with arguments should use getopt[/-][+][FEATURE] Scripts with arguments should use getopt/getopts[/+][-][FEATURE] Scripts with arguments should use getopt/getopts[/-][+][FEATURE] Scripts with arguments should use getopts[/+]jajanusz commentedon Mar 26, 2020
@crazoes Thanks, I've updated description to use
getoptsinstead ofgetopt, I think it's better cos it's in posix standard whilegetoptis not. Are you ok with that?jajanusz commentedon Mar 26, 2020
Also there is one script that uses it already:
sof/scripts/scan/clang-scan-build-xtensa.sh
Line 37 in 9d9620a
kv2019i commentedon Dec 17, 2025
No activity in 5 years, closing. Please reopen if still relevant.