public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/17098] In program using unique_ptr, identifier 'tuple' cannot be used (problem with variadic templates?)
Date: Wed, 27 Dec 2023 17:53:24 +0000 [thread overview]
Message-ID: <bug-17098-4717-6YOT1lLsIL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17098-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17098
--- Comment #4 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to Tom Tromey from comment #3)
> Maybe the canonical bug for this is bug#17272?
> There are also several bugs open about exposing this to the Python API.
> The fix seems to be stalled.
As I understand it, the problem here is about tuple being also the name of
the include file, and that's why you get a syntax error.
And according to c-exp.y, this behavior is intentional:
```
/* If we found a field on the "this" object, or we are looking
up a field on a struct, then we want to prefer it over a
filename. However, if the name was quoted, then it is better
to check for a filename or a block, since this is the only
way the user has of requiring the extension to be used. */
```
So if no variable is found by the name, but one of the files has that name,
it assumes the file is meant.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-12-27 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 10:17 [Bug c++/17098] New: " Marc.van-Leeuwen at math dot univ-poitiers.fr
2023-12-27 13:10 ` [Bug c++/17098] " ssbssa at sourceware dot org
2023-12-27 13:29 ` ssbssa at sourceware dot org
2023-12-27 16:52 ` tromey at sourceware dot org
2023-12-27 17:53 ` ssbssa at sourceware dot org [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=bug-17098-4717-6YOT1lLsIL@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).