From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 7AF2A3870899; Fri, 24 Mar 2023 09:45:21 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7AF2A3870899
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1679651121;
	bh=d8wfvpu7xVEuhWqbUzQUNG+A8+diCLYg3ZTU1JNfk9o=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Gm4GtMyqAgcJzJ9Ra8dIZItOnqdXt9ZLAU8vu7JpFJLgf20AEEUpXMSXJsE2WC0Eo
	 vgB4FYx3iC+BojafXKLoX/GYx9FNNa3wBGEfB+NSSqF2H+5gGtAK5f4BGGpAnkhnXJ
	 a66ZWvq5IGDDJA1/orpB3QQ00YfHM2jkNt6Y7eEA=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: libabigail
X-Bugzilla-Component: default
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gprocida at google dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: dodji at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-30260-9487-Q4WUzN15sc@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30260-9487@http.sourceware.org/bugzilla/>
References: <bug-30260-9487@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <libabigail.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D30260

--- 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 separ=
ated
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;

--=20
You are receiving this mail because:
You are on the CC list for the bug.=