From -2594461167937224327 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,7eaa8faac8da5016 X-Google-Attributes: gidf78e5,public From: Pete Becker Subject: Re: Defect Report: member == in container iterators considered harmful Date: 1999/08/17 Message-ID: <37B98C2E.E3A1EA71@acm.org>#1/1 X-Deja-AN: 513848996 Content-Transfer-Encoding: 7bit Approved: Valentin Bonnard References: <7p4nj8$n3u@enews4.newsguy.com> X-Original-Date: Tue, 17 Aug 1999 12:22:06 -0400 X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Organization: Road Runner X-Auth: PGPMoose V1.1 PGP comp.std.c++ iQBVAwUAN7mMtawEuYhIxRhxAQEhmQH/TrXkRLjM0SueKyWqzWauGn8NKG+rOblp j20Y0be/WSYOBbHU4vjkB9eOvVXOoIxhVRRuXhcVJN9+434fmo6+Dw== =iM3c Mime-Version: 1.0 Newsgroups: comp.std.c++ Darin Adler wrote: > > [ moderator's note: forwarded to C++ committee for handling. -sdc ] > > Some standard containers define iterator classes to fulfill the requirements > described in 23.1 [lib.container.requirements]. This states that iterator > must be convertible to const_iterator. However, the following code is not > guaranteed to work: > > bool check_equal(std::deque::iterator i, > std::deque::const_iterator ci) > { > return i == ci; > } > Agreed. But the begin and end iterators that you get from a container are of the same type, and they work just fine for the standard STL idioms. Why do you need to do this? What coding practices does it support? -- Pete Becker Dinkumware, Ltd. http://www.dinkumware.com --- [ 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 ]