Date: Wed, 6 Oct 1999 11:30:02 -0700 (PDT) From: "Justin T. Gibbs" <gibbs@caspian.plutotech.com> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/13383 sys/netinet/in.h violates C++ spec. Message-ID: <199910061830.LAA40079@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/13383; it has been noted by GNATS. From: "Justin T. Gibbs" <gibbs@caspian.plutotech.com> To: Jacques Vidrine <n@nectar.com> Cc: Thomas David Rivers <rivers@dignus.com>, freebsd-gnats-submit@freebsd.org, gibbs@plutotech.com Subject: Re: bin/13383 sys/netinet/in.h violates C++ spec. Date: Wed, 06 Oct 1999 12:23:29 -0600 >On 6 October 1999 at 13:19, Thomas David Rivers <rivers@dignus.com> wrote: >> I think gcc 2.95.1 "improved" it's standards conformance. It is >> now diagnosing errors previous versions didn't. >> >> Could that be the issue? > >No, see the text of this PR. To summarize: > >g++ version gives error >2.95 yes (according to Justin) >2.7.2.3 no (test case in PR) >2.91.66 no (test case in PR) >2.95.1 no (test case in PR) > >I don't have a position on which is CORRECT, but obviously the latter >is more useful. > >Further, perhaps there is some confusion with regards to the compiler >version Justin is using, or perhaps there is a test case that Justin >has that produces the error. > >Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org [waterboy::pluto]$ /build/gibbs/local/bin/g++ foo.cc -o foo foo.cc:6: redefinition of `struct ip_opts' /usr/include/netinet/in.h:292: previous definition here foo.cc:8: ANSI C++ forbids data member `ip_opts' with same name as enclosing class [waterboy::pluto]$ /build/gibbs/local/bin/g++ -Wall foo.cc -o foo foo.cc:6: redefinition of `struct ip_opts' /usr/include/netinet/in.h:292: previous definition here foo.cc:8: ANSI C++ forbids data member `ip_opts' with same name as enclosing class [waterboy::pluto]$ /build/gibbs/local/bin/g++ -v Reading specs from /build/gibbs/local/lib/gcc-lib/i386-portbld-freebsd3.2/2.95.1/specs gcc version 2.95.1 19990816 (release) in.h does not have any C++ protection, so if in.h has invalid C++ in it, the compiler is right to complain. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199910061830.LAA40079>