On Tue, Oct 27, 2015 at 7:30 PM, Joseph Myers <jos...@codesourcery.com> wrote:
Hello Joseph.
> On Tue, 27 Oct 2015, Andres Tiraboschi wrote:
>
>> While we start a discussion with the C committee regarding the standarization
>> of this feature, we think that this is a useful nonstandard addition to be
>> early adopted.
>
> Are you raising the issue with WG14 in Kona this week? I'd be wary of
> this sort of extension without positive views from WG14 / WG21.
I presented the issue in the WG21 std-proposal mailing list and the general
consensus was that I should ask WG14 first. The problem is that this issue
is C++ only so I'm kind of stuck. Anyway I already asked the convener about
this (David Keaton) and I'm waiting for his answer. I don't know another way
to raise the issue in WG14 since I'm not attending the Kona meeting. Are you a
member of the WG14 committee?
Considering that this is an opt-in feature controlled by a command line flag,
couldn't be just another GNU extension meanwhile? The issue is relevant in C++.
>
> This patch is, in any case, missing sufficient testcases and
> documentation. Testcases need to include lots of variations that make
OK, agreed. We'll create more test cases and documentation.
> clear whether the \, must appear literally like that without whitespace,
Yes, there should not be whitespace between the \ and the comma.
> or whether there might be space between them, or they might come from
> expansions of separate macros, etc.; formatting of the patch also appears
Something worth to mention is that the \, is only escaped at top-level in terms
of parenthesis, so
mymacro(function(x \, y))
will not be escaped with this patch, so behavior is not altered in such case.
> messed up. Testcases also need to include cases that are valid with and
> without the option but with different semantics, to make clear that the
> option and its absence do the right thing in such cases. Documentation
> should include precise proposed standard wording to make such semantic
> issues clear; that's the level at which this would need to be defined.
Thanks,
Daniel.
>
> --
> Joseph S. Myers
> jos...@codesourcery.com
--
Daniel F. Gutson
Chief Engineering Officer, SPD
San Lorenzo 47, 3rd Floor, Office 5
Córdoba, Argentina
Phone: +54 351 4217888 / +54 351 4218211
Skype: dgutson
LinkedIn: http://ar.linkedin.com/in/danielgutson
