On 09/23/2011 09:48 AM, Jeff Squyres wrote:
> However, we ultimately discarded it when someone showed a real-world code that used *multiple* wrapper compilers (i.e., one wrapper compiler invoked another, which, in turn, invoked another, and then finally invoked the real/underlying compiler). Who gets the tokens before "--"?
> You could certainly have a command line like:
> wrapper1 --foo -- --opions-for-wrapper2 -- --options-for-wrapper3 -- foo.c -o foo
> But that seems exceedingly distasteful.
and quite likely confusing.
> I'm afraid I don't remember the specific application / middleware that was used in our decision point not to support "--", but I should point out it was very much in line with our original philosophy: only understand --showme and pass everything else, including "--", to the underlying executable (which may just happen to be another wrapper or something else that might understand "--").
> Given that MPI can be used with other middleware, we decided that the best approach was minimalistic and allow our flags to be extracted if needed. Those two options seemed to cover all cases, even if they -- unfortunately -- aren't portable.
a purposeful and justified design choice is surely better than incidents :)