Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <43F5F704.7040000@roguewave.com>
Date: Fri, 17 Feb 2006 09:17:08 -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 lib.set.intersection
References: <43F4A426.9050001@moscow.vdiweb.com>
In-Reply-To: <43F4A426.9050001@moscow.vdiweb.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Anton Pevtsov wrote:
> The attached file contains the test for the lib.set.intersection
> algorithm.

Thank you. Committed thus:
http://svn.apache.org/viewcvs.cgi?rev=378555&view=rev

[...]
> struct SetIntersectionTestBase
> {
>     virtual ~SetIntersectionTestBase() {}
> 
>     const char* iter_names [3];
> 
>     // invokes set_intersection
>     virtual X*
>     set_intersection (const X*, const X*, const X*, const X*, 
>                       X*, X*, const Less*) const {
>         RW_ASSERT (!"test logic error");

FYI: there is no need to provide a definition for a virtual function
in the base class as long as it is overridden in the base class. In
cases when the function must be overridden it's better to make it
pure virtual. (The reason 25.merge.cpp does define the virtual
functions in the base rather than make them pure is because each
derived class overrides only one of the two functions; the one that
is not overridden is not called on the object that doesn't override
it).

Martin