> Why would you care about the link line? It does no harm to have it slightly longer.
It's just aesthetically more pleasing is all. There are limits to the maximum length of a command-line execution. I have been told that MAME actually runs into this issue and has to build several library blocks to get the final link phase to work. I'm nowhere near it even at five emulator cores, and kitchen sink style audio/video/input drivers that every API available on each OS for user choice.
Given this issue, I'm probably going to revert that change.
> I checked out getopt.c and...really? I mean, sure, the functionality is ideal, but the internal getopt function is such a giant that I don't see the problem with just using a much simpler parser that probably handles things just as well outside of the issue in spacing.
There's two very distinct classes of programmers in the world.
There's the kind that looks at programming like building with legos. Find all the pieces you want, snap them together! You end up with a very pretty lego statue
in a few days. This is the kind that would say "just use getopt.c from another project."
Then there's the kind that wants to learn everything about programming, how everything works, and wants to pare everything down to only what's required and nothing more. People that look for perfection. You end up with masterpieces
, but they take you months instead of days to create. This is the kind that would say "write your own argument parser that does only what you want it to do."
There's really nothing wrong with either approach. The big problem is that one side (usually from the former camp, but not always) loves to denigrate the other side. Humans just seem to have a huge issue with accepting that people who disagree with them aren't malicious, crazy, and/or incompetent.