Article View: gnu.g++.help
Article #790Re: NULL = ((void *)0) problem
From: Joe Buck
Date: Tue, 10 Oct 1995 17:26
Date: Tue, 10 Oct 1995 17:26
20 lines
1245 bytes
1245 bytes
rjf@infograph.com (rjf) writes: >This thread (which I started) has been very interesting, and I >actually understand some of it -- however, I am curious -- is the >assertion by the GNU compiler that ANSI does not allow the conversion >of ((void *)0) to some object pointer valid? Yes -- C++ has been this way for a very long time. Older g++ releases did not enforce the rule. Assigning a (void *) to some other type of pointer requires a cast in C++. Always has. >Is this ANSI's position? The committee has not changed the existing rule from the ARM, yes. -- -- Joe Buck <jbuck@synopsys.com> (not speaking for Synopsys, Inc) Anagrams for "information superhighway": Enormous hairy pig with fan A rough whimper of insanity
Technical Details
Message-ID:
<45eac6$ech@hermes.synopsys.com>Path:
arc1-ca.pugleaf.net!news.synopsys.com!jbuckReferences:
<435jf3$1iq@globe.indirect.com> <45666e$amf@engnews2.Eng.Sun.COM> <KANZE.95Oct9120444@slsvgqt.lts.sel.alcatel.de> <RJF.95Oct09140502@krusty>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!news.synopsys.com!jbuck From: jbuck@synopsys.com (Joe Buck) Newsgroups: gnu.g++.help,comp.lang.c++ Subject: Re: NULL = ((void *)0) problem Date: 10 Oct 1995 17:26:30 GMT Organization: Synopsys Inc., Mountain View, CA 94043-4033 Message-ID: <45eac6$ech@hermes.synopsys.com> References: <435jf3$1iq@globe.indirect.com> <45666e$amf@engnews2.Eng.Sun.COM> <KANZE.95Oct9120444@slsvgqt.lts.sel.alcatel.de> <RJF.95Oct09140502@krusty> NNTP-Posting-Host: deerslayer.synopsys.com