Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@stdcxx.apache.org
Received-SPF: pass (athena.apache.org: domain of msebor@gmail.com designates
 64.233.166.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:organization:user-agent:mime-version:to
         :subject:references:in-reply-to:content-type
         :content-transfer-encoding:sender;
        b=wze9yDL7pu1HGSq2eR3PBvFPkTMsYUzIMXlOL1ba+eIjDb9e4rKidHE82K+D17nP2C
         LrFOzlb4zJmmBa6pt3rRafKxyhPEL90qUHlrHERBOzp9R9HNxih0GFchejgcemuht1lO
         a7OieNSYjF84hhmMGreelLMfhWnh+GBshizuo=
Message-ID: <48778919.4090405@roguewave.com>
Date: Fri, 11 Jul 2008 10:23:53 -0600
From: Martin Sebor <sebor@roguewave.com>
Organization: Rogue Wave Software, Inc.
User-Agent: Thunderbird 2.0.0.14 (X11/20080501)
MIME-Version: 1.0
To: dev@stdcxx.apache.org
Subject: Re: Potential eccp-3.9 bug
References: 
 <CFFDD219128FD94FB4F92B99F52D0A4901E0FC20@exchmail01.Blue.Roguewave.Com>
 <487680E1.5070006@roguewave.com>
 <CFFDD219128FD94FB4F92B99F52D0A4901E0FC22@exchmail01.Blue.Roguewave.Com>
 <48769C47.1050509@roguewave.com>
 <CFFDD219128FD94FB4F92B99F52D0A4901E0FC25@exchmail01.Blue.Roguewave.Com>
 <4876CEB5.9080502@roguewave.com>
 <CFFDD219128FD94FB4F92B99F52D0A4901E0FC26@exchmail01.Blue.Roguewave.Com>
In-Reply-To: 
 <CFFDD219128FD94FB4F92B99F52D0A4901E0FC26@exchmail01.Blue.Roguewave.Com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: Martin Sebor <msebor@gmail.com>

Travis Vitek wrote:
>  
> 
> Martin Sebor wrote:
>> Travis Vitek wrote:
>>>  
>>>
>>> This all seems to work when using the trait with a 
>>> non-template type. If you want to use a template, it
>>> has to be instantiated first. I think I'm going to
>>> put the Edison compiler port on hold for now.
>> Yeah, it doesn't seem quite stable enough. Let's see what they
>> come back with, but unless there's something we're missing it
>> might be best to wait for 3.10. I assume HP aCC 6 isn't any
>> better?
> 
> I got things working quite well on aCC 6.16. It doesn't support any of
> the built-ins, but I'm able to work around a lot of those issues.

AFAICS, it's based on EDG eccp 3.8, so it's likely to have the same
problems as those we discussed yesterday. A simple test case using
__is_empty(int) compiles fine, but as expected the compiler spits
out the same error for the __is_empty (S<0>) case as we saw eccp
3.9 do. Let me try to find out when HP plans to upgrade to the
latest EDG front end.

> The
> one big issue is that I can't implement __rw_is_class<> accurately
> without __is_class(). Without this I get compile failures in the
> implementation of some traits that require an accurate implementation.
> This causes 20.meta.unary.prop.cpp to fail to compile.
> 
> Now that we have eccp-3.10.1 I'll have another go at it.
> 
> Thanks,
> 
> Travis