Return-Path: Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org Received: (qmail 84868 invoked from network); 28 Nov 2007 20:32:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Nov 2007 20:32:18 -0000 Received: (qmail 88919 invoked by uid 500); 28 Nov 2007 20:32:06 -0000 Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org Received: (qmail 88910 invoked by uid 500); 28 Nov 2007 20:32:06 -0000 Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: stdcxx-dev@incubator.apache.org Delivered-To: mailing list stdcxx-dev@incubator.apache.org Received: (qmail 88899 invoked by uid 99); 28 Nov 2007 20:32:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Nov 2007 12:32:06 -0800 X-ASF-Spam-Status: No, hits=-99.8 required=10.0 tests=ALL_TRUSTED,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Nov 2007 20:31:46 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 826A8714243 for ; Wed, 28 Nov 2007 12:31:43 -0800 (PST) Message-ID: <12071797.1196281903531.JavaMail.jira@brutus> Date: Wed, 28 Nov 2007 12:31:43 -0800 (PST) From: "Travis Vitek (JIRA)" To: stdcxx-dev@incubator.apache.org Subject: [jira] Commented: (STDCXX-645) stream iterators into different streams compare equal In-Reply-To: <475308.1194106130752.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/STDCXX-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546374 ] Travis Vitek commented on STDCXX-645: ------------------------------------- In most cases the iterator is going to be used in a loop which calls op!= and op++ repeatedly. In this case op== would get called one time more than op++. Of course there are some scenerios where op++ is called more frequently than op== [std::distance or std::advance], but I don't believe that those are the most common use cases for an istream_iterator. If we fix op++, then op== becomes a pointer comparison and op++ gets an additional assignment. I think fixing op++ would be the preferred solution if we are just counting instructions. > stream iterators into different streams compare equal > ----------------------------------------------------- > > Key: STDCXX-645 > URL: https://issues.apache.org/jira/browse/STDCXX-645 > Project: C++ Standard Library > Issue Type: Bug > Components: 24. Iterators > Affects Versions: 4.1.3, 4.2.0 > Reporter: Mark Brown > > As Travis says in his reply to my post here: > http://www.nabble.com/stream-iterators-into-different-streams-compare-equal--tf4721505.html#a13498487: > Given 24.5.1.1 p1 and p2, it is pretty clear to me that the two iterators are both non-end-of-stream type, and they are both created on different streams. The streams are different, so the iterators should not compare equal. I guess one could claim that 24.5.1.2 p6 conflicts with 24.5 p3 because 'end-of-stream' isn't clearly defined, but in this particular case that doesn't matter. > This program aborts with stdcxx but not with gcc: > #include > #include > #include > int main () > { > std::istringstream a ("1"); > std::istream_iterator i (a); > std::istringstream b ("2"); > std::istream_iterator j (b); > assert (!(i == j)); > } -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.