From: "gprocida at google dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30260] add support for pointer-to-member types
Date: Fri, 24 Mar 2023 09:45:20 +0000 [thread overview]
Message-ID: <bug-30260-9487-Q4WUzN15sc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30260-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30260
--- Comment #2 from gprocida at google dot com ---
Naming of these types appears to follow all the same rules as naming normal
pointer types, including when parentheses are needed.
pointer to: ... * ...
becomes
pointer to X member: ... X::* ...
Extra complications are:
1. the syntax immediately to the left of the * or X::* may need to be separated
by a space
int*x; // no space needed before *
int X::*x; // space is needed before X
int (X::*x)(); // space would look odd inside the bracket
2. this is normally written as just the tag, without struct / class / union
but you might want to include the keyword for clarity or for simplicity of
coding
int struct X::*x;
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-24 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 11:37 [Bug default/30260] New: " gprocida at google dot com
2023-03-22 12:29 ` [Bug default/30260] " gprocida at google dot com
2023-03-24 9:45 ` gprocida at google dot com [this message]
2023-10-24 15:24 ` dodji at redhat dot com
2023-10-24 15:43 ` woodard at redhat dot com
2023-11-30 16:35 ` dodji at redhat dot com
2023-11-30 21:51 ` gprocida at google dot com
2023-12-01 16:03 ` dodji at redhat dot com
2023-12-01 16:04 ` dodji at redhat dot com
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=bug-30260-9487-Q4WUzN15sc@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.org \
/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).