From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21345 invoked by alias); 11 Oct 2011 19:36:37 -0000 Received: (qmail 21297 invoked by uid 22791); 11 Oct 2011 19:36:36 -0000 X-SWARE-Spam-Status: No, hits=-7.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 11 Oct 2011 19:36:21 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p9BJaJh7016179 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 11 Oct 2011 15:36:20 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p9BJaJ8w010019; Tue, 11 Oct 2011 15:36:19 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id p9BJaIK1005523; Tue, 11 Oct 2011 15:36:18 -0400 From: Tom Tromey To: Keith Seitz Cc: "gdb-patches\@sourceware.org ml" Subject: Re: [RFA] c++/13225 References: <4E9495DB.8010109@redhat.com> Date: Tue, 11 Oct 2011 19:36:00 -0000 In-Reply-To: <4E9495DB.8010109@redhat.com> (Keith Seitz's message of "Tue, 11 Oct 2011 12:15:39 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-10/txt/msg00330.txt.bz2 >>>>> "Keith" == Keith Seitz writes: Keith> This occurs because the parser interprets "0" as an integer, and the Keith> evaluator does not allow integer to pointer conversion. I cannot Keith> really think of a reason why gdb shouldn't be more permissive of this, Keith> as long as the INT will fit into a pointer. Sami updated overloading resolution to more faithfully follow the C++ spec. So, I think it would be useful to justify this patch in terms of the standard. Tom