From owner-freebsd-hackers Thu Sep 14 9:13:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 0863A37B422 for ; Thu, 14 Sep 2000 09:13:29 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA04099; Thu, 14 Sep 2000 09:12:04 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA02297; Thu, 14 Sep 2000 09:12:04 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 14 Sep 2000 09:12:04 -0700 (PDT) Message-Id: <200009141612.JAA02297@vashon.polstra.com> To: hackers@freebsd.org Cc: n@nectar.com, archie@whistle.com Subject: Re: c++ error In-Reply-To: <20000914083032.B16624@spawn.nectar.com> References: <200009140019.RAA04988@bubba.whistle.com> <200009140036.RAA01292@vashon.polstra.com> <20000913230227.A15302@spawn.nectar.com> <20000914083032.B16624@spawn.nectar.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000914083032.B16624@spawn.nectar.com>, Jacques A. Vidrine wrote: > In summary, gcc has a kluge to work around a bug in the C++ > standard. It looks like you and Justin Archie. > have both found edge cases where the gcc kluge loses. If you can > come up with a reasonable test case that reproduces the problem, > perhaps it can be PR'd to the GCC folks? Actually, I don't have a test case. I was only able to make it fail when I moved out of /usr/include -- which disables the gcc kludge. I hope that Archie will be able to come up with a test case that demonstrates the failure. BTW, Archie, there are 3 places in the gcc code which can produce that diagnostic: 1 in "cp/class.c" and 2 in "cp/decl.c". Search for "with same name as" and you'll find them. It would be useful to find out which one of those is the culprit in your failing case. > As per the PR, I'm against #ifdef'ing structures like ip_opts for C++, > since it is likely that a later C++ standard will be corrected. I can't argue with that. I don't like my "solution" very much either. :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message