Re:The growth of command-line options, 1979-Present
by carterehsmith on Tuesday March 03, 2020 @07:28PM
(#22480135)
Is there a better way? Can we make gcc with less options, while still catering to all the use cases.
Re:The growth of command-line options, 1979-Present
by Paul-ish on Tuesday March 03, 2020 @09:18PM
(#22480676)
That might not be possible. What if instead we created a configuration tool that intelligently passed the correct options for you.
Re:The growth of command-line options, 1979-Present
by carterehsmith on Tuesday March 03, 2020 @09:23PM
(#22480685)
Could that tool magically reduce the number of options? That would be quite a tool.
Re:The growth of command-line options, 1979-Present
by bentcorner on Tuesday March 03, 2020 @10:05PM
(#22480873)
You could subdivide what gcc does into other utilities each with a smaller api.
Re:The growth of command-line options, 1979-Present
by TeMPOraL on Wednesday March 04, 2020 @12:18AM
(#22481387)
This way lies Node.js. You'll end up with a complex config file just to orchestrate all these smaller utilities.
Re:The growth of command-line options, 1979-Present
by Paul-ish on Wednesday March 04, 2020 @02:18PM
(#22486943)
Yes. We will call it autotools.
The true winner is probably gcc though, which was unfairly excluded from competition. Over 1000 options is excellent work.