Mailing-List: contact issues-help@stdcxx.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@stdcxx.apache.org
Message-ID: <1886366749.1210884655546.JavaMail.jira@brutus>
Date: Thu, 15 May 2008 13:50:55 -0700 (PDT)
From: "Martin Sebor (JIRA)" <jira@apache.org>
To: issues@stdcxx.apache.org
Subject: [jira] Updated: (STDCXX-78) std::copy() doesn't detect overlapping
 ranges
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/STDCXX-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Sebor updated STDCXX-78:
-------------------------------

              Severity: Usability
     Affects Version/s: 4.1.3
                        4.1.4
                        4.2.0
                        4.2.1
         Fix Version/s: 4.3
    Remaining Estimate: 4h
     Original Estimate: 4h

Let's see if this is worth doing in 4.3.

> std::copy() doesn't detect overlapping ranges
> ---------------------------------------------
>
>                 Key: STDCXX-78
>                 URL: https://issues.apache.org/jira/browse/STDCXX-78
>             Project: C++ Standard Library
>          Issue Type: Improvement
>          Components: 25. Algorithms
>    Affects Versions: 4.1.2, 4.1.3, 4.1.4, 4.2.0, 4.2.1
>         Environment: all
>            Reporter: Martin Sebor
>            Priority: Minor
>             Fix For: 4.3
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Quoting from the response to the following post:
> http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200511.mbox/%3c4D6A8407B7AC6F4D95B0E55C4E7C4C6202EEFD7E@exmsk.moscow.vdiweb.com%3e
> -------- Original Message --------
> Subject: Re: questions about the lib.alg.copy test
> Date: Wed, 30 Nov 2005 17:33:10 -0700
> From: Martin Sebor <sebor@roguewave.com>
> To: stdcxx-dev@incubator.apache.org
> References: <4D6A8407B7AC6F4D95B0E55C4E7C4C6202EEFD7E@exmsk.moscow.vdiweb.com>
> Anton Pevtsov wrote:
> [...]
> > 
> > 2. The copy algorithm can work in case when the destination range
> > overlaps the source range (of course, first position of the source range
> > should not be contained in the destination range). Current version
> > doesn't contain special test for this case, but I prefer to have such
> > test. What do you think about it?
> The requirement in 25.2.1, p3 is that "result shall not be in the
> range [first, last)." The algorithm doesn't detect violations of
> this requirement but it probably should in debug mode. This would
> be a useful enhancement in general. Let me file an enhancement for
> it.
> Martin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.