[Bug]: --cpp-lines does not work if -g appears later in command line

[mppf]

Summary of Problem

Description:
I'm trying to debug something and need to look at the C code. If I compile with chpl program.chpl --savec=tmp --no-cpp-lines -g then I still see the #line directives. But, if I put the -g before --no-cpp-lines then it works.

(A bonus task related to this issue would be to come up with a better user-facing name than -cpp-lines; that can be misinterpreted as "Show me the C++ lines" but it actually means "Include #line directives so you see .chpl line numbers").

Is this issue currently blocking your progress?
No

Steps to Reproduce

Source Code:

any

Compile command:

see above

Associated Future Test(s):
TODO

Configuration Information

chpl version 2.3.0

[bradcray]

I'd consider this to be working as intended, in the sense that we typically process flags in order and permit the effects of the flags to override one another silently. For example chpl --fast --bounds-checks will do all the things --fast normally does, including disabling bounds checks, and then --bounds-checks overrides that default.

Here, -g has the effect of turning on -cpp-lines (for non-developers) as documented on the man page:

       -g, --[no-]debug
          Causes the generated C code to be compiled with debugging turned on.
          If you are trying to debug a Chapel program, this flag is virtually
          essential along with the --savec flag. This flag also turns on the
          --cpp-lines option unless compiling as a developer (for example, via
          --devel).