From -3307914087705689586 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,f1dec9ce20a9c98f X-Google-Attributes: gidf78e5,public From: Francis Glassborow Subject: Re: null pointers (was: Why's of C++ -- Part 1) Date: 1999/08/24 Message-ID: #1/1 X-Deja-AN: 516719502 Approved: Fergus Henderson References: <7opqvm$vpa$1@news.hal-pc.org> <37B7C714.44E4EFB4@lucent.com> <7pcoem$105@abyss.West.Sun.COM> <7pdh80$qaf$1@engnews1.eng.sun.com> <7phdj7$4oj@abyss.West.Sun.COM> <2yG4gOAhsRv3EwJN@robinton.demon.co.uk> <37C15258.8C236E32@wizard.net> X-Original-Date: Mon, 23 Aug 1999 18:29:00 +0100 X-Complaints-To: news@news.unimelb.edu.au X-Trace: izvestia.its.unimelb.edu.au 935525584 32438 128.250.29.17 (24 Aug 1999 20:13:04 GMT) Organization: Southfield Microcomputer SS X-Auth: PGPMoose V1.1 PGP comp.std.c++ iQBFAgUAN8L8vuEDnX0m9pzZAQHfGAF/foOpgYb37fyTKCBoOJ+aqN3bvzpSeiij DBKGVczR4hHgmuLCbcbkjdH2ennA/GO5 =kiHg Mime-Version: 1.0 Reply-To: Francis Glassborow NNTP-Posting-Date: 24 Aug 1999 20:13:04 GMT Newsgroups: comp.std.c++ In article <37C15258.8C236E32@wizard.net>, James Russell Kuyper Jr. writes >However, it must compare equal to the null pointer constant (after >suitable conversions). Code that does anything with it other than >checking it for equality (after suitable conversions) is in trouble >anyway. Why? Has C++ provided some special way round this? We have been round this loop many times in C. Francis Glassborow Journal Editor, Association of C & C++ Users 64 Southfield Rd Oxford OX4 1PA +44(0)1865 246490 All opinions are mine and do not represent those of any organisation --- [ comp.std.c++ is moderated. To submit articles, try just posting with ] [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html ]