ghc command line arguments parsing
svenpanne at gmail.com
Fri Aug 19 07:01:02 UTC 2016
2016-08-18 19:59 GMT+02:00 Harendra Kumar <harendra.kumar at gmail.com>:
> [...] It only parses a flag which takes an argument. [...]
o_O AFAICT, this is even more non-standard and quite surprising...
> As I explained above, I would prefer to keep this bug :-) and document it
> especially for runghc as a better alternative to --ghc-arg=foo . [...]
While I partly understand your motivation, convenience is often the worst
reason for doing something. Consistency is IMHO infinitely more valuable
than having various inconsistent ad-hoc "convenient" shortcuts here and
there. If you look around the tool landscape, commandline argument parsing
is already less consistent than it should be (try e.g.
ps/tar/unzip/df/java/git/...), and I don't think we should make this
situation worse by adding yet another variation.
As long as we have a way to pass arguments down the pipeline (as we
obviously have), thing are fine IMHO. This situation is not much different
from the common -Wl,foo option for GCC and friends to pass arguments to the
linker. And to be honest: How often do you really *type* long commandlines
compared to putting them into some kind of script?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ghc-devs