Hi Rene,

Maybe I am missing something completely, but my understanding of Command
Line Portability
<https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2023/p2656r2.html#_command_line_portability>
section is
that it allows the user to write a response file _once_ and use it with any
tool.
My understanding is that the file and its structure is human readable and
that each tool interprets it as it should.

Following this logic, I would expect to see the *options* part specified
precisely, giving tools the opportunity to implement the best they can.
e.g, instead of this:
{ "options": [ "fPIC", { "O": "0" }, "fno-inline", { "W": [ "all", "error" ]
}, "g", { "I": [ "util/include" ] }, "c" ] }

I would love to see this:
{ "options": [ { "position_independent_code": true }, { "optimization":
"none" }, { "allow_inline", false }, { "warnings": [ "all", "error" ] }, {
"debug" : true, { "includes": [ "util/include" ] }, {"compile" : true } ] }

All keys are part of the standard and are reserved words.


Ran.


On Mon, Nov 27, 2023 at 3:01 PM René Ferdinand Rivera Morell via SG15 <
sg15_at_[hidden]> wrote:

> I'm looking for feedback for one of the wish items from the Ecosystem
> IS goals list "Structured Response Files"
> (https://wg21.link/P2656#_command_line_portability). Here's a rough
> draft of such a capability <https://wg21.link/D3051R0>.
>
> --
> -- René Ferdinand Rivera Morell
> -- Don't Assume Anything -- No Supone Nada
> -- Robot Dreams - http://robot-dreams.net
> _______________________________________________
> SG15 mailing list
> SG15_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg15
>