From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Avoiding metavariable confusion for duplicate identifiers?
Date: Sun, 29 Jun 2025 07:30:58 +0200 [thread overview]
Message-ID: <728b184c-a7c5-41f1-8f15-b9fc139c2e3a@web.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2506282320450.50494@hadrien>
>> Under which circumstances would you put such identifiers into different name spaces?
>
> None. Doing something like you suggest would reduce the expressiveness of
> the language,
I do not follow such a concern.
> and doesn't seem at all like a good idea.
1. Is there a general need to distinguish member names anyhow from other identifiers?
https://cppreference.com/w/c/language/operator_member_access.html#Member_access_through_pointer
2. Do you plan to extend the support for the C++ key word “namespace”?
https://cppreference.com/w/cpp/language/namespace.html
Regards,
Markus
prev parent reply other threads:[~2025-06-29 5:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-28 14:11 [cocci] Avoiding metavariable confusion for duplicate identifiers? Markus Elfring
2025-06-28 14:39 ` Julia Lawall
2025-06-28 19:21 ` Markus Elfring
2025-06-28 19:32 ` Julia Lawall
2025-06-28 19:37 ` Markus Elfring
2025-06-28 19:43 ` Julia Lawall
2025-06-28 19:50 ` Markus Elfring
2025-06-28 19:58 ` Julia Lawall
2025-06-28 20:08 ` Markus Elfring
2025-06-28 20:44 ` Markus Elfring
2025-06-28 21:21 ` Julia Lawall
2025-06-29 5:30 ` Markus Elfring [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=728b184c-a7c5-41f1-8f15-b9fc139c2e3a@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).