From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9BE9E3858CD1; Wed, 27 Dec 2023 17:53:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9BE9E3858CD1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1703699605; bh=ciRo/ej55MqzD+8uP4d/I6rquBOxRGl+UP59vgehF90=; h=From:To:Subject:Date:In-Reply-To:References:From; b=YMlhysz+vWLpN4KekAXD6UCY1GqkQZ/VadofVbyZWeTefxcSJb8giE8fGIutB/oxS fWAiwY1yGsSUX+bucNe5ChBSzEajdnAAHQzpcVMyx9HhQNyJYK3250HtEwszT44Pwc xdSVw+DBnH50cktxZmAtA4zsNAtX9W/XK1miacqM= From: "ssbssa at sourceware dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: 7.10 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ssbssa at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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: https://sourceware.org/bugzilla/show_bug.cgi?id=3D17098 --- Comment #4 from Hannes Domani --- (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. --=20 You are receiving this mail because: You are on the CC list for the bug.=