Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <4425C88F.1060406@roguewave.com>
Date: Sat, 25 Mar 2006 15:47:43 -0700
From: Martin Sebor <sebor@roguewave.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
MIME-Version: 1.0
To: stdcxx-dev@incubator.apache.org
Subject: Re: test for 21.string.copy
References: <4422C957.4030909@moscow.vdiweb.com>
In-Reply-To: <4422C957.4030909@moscow.vdiweb.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Anton Pevtsov wrote:
> The latest version of the test is attached. I plan to commit it to the
> svn, ok?

Actually, there are a few more simplifying improvements that I think
we still ought to make. First, we can use the third argument to copy
(pos) to distinguish between the two overloads. When pos is negative
(say, -1) the two argument overload will be invoked. Otherwise, the
test function will invoke the three-argument overload. That will
allow us to eliminate the (redunant) function tag CTag.

Second, in the test function, I would like to use rw_match() instead
of Traits::compare() to verify that the contents of the buffer match
the expected result. This will let us avoid widening the expected
result and enable us to display the offset of the first mismatched
character (if any) in the rw_assert() diagnostic message.

Lastly, in the test_cases array, I think the order of data should
match the order of function arguments (i.e., controlled sequence,
n, the second argument to copy, and pos, the third argument which
should be -1 for the test cases exercising the two-argument overload
of the member function).

Oh, and one minor nit :) If you could move the indented #ifndef
reprocessor directives to the left margin that would be great :)

Thanks!
Martin