> The second argument to BOOST_PROTO_DEFINE_OPERATORS is a domain. When
> defining a domain you (usually) specify a generator with an expression
> wrapper. What are you using for a domain, and how do you define it?
>
> When I want an end-user-friendly terminal type, I derive it from the
> express
On 2/13/2011 2:55 AM, Nate Knight wrote:
>
> I have some external non-proto terminals I've adapted using
> BOOST_PROTO_DEFINE_OPERATORS. I was trying to figure out how to get
> the terminals picked up by the operator overloads without importing
> them all from the namespace they are defined in ev
> On 2/12/2011 7:17 AM, Nate Knight wrote:
>> I see in the Proto documentation a trick for getting the Proto operator
>> overloads found by ADL using something like
>>
>> template
>> struct my_complex
>> {
>>BOOST_PROTO_EXTENDS(
>>typename proto::terminal >::type
>> , my_complex
On 2/12/2011 7:17 AM, Nate Knight wrote:
> I see in the Proto documentation a trick for getting the Proto operator
> overloads found by ADL using something like
>
> template
> struct my_complex
> {
> BOOST_PROTO_EXTENDS(
> typename proto::terminal >::type
> , my_complex
>
I see in the Proto documentation a trick for getting the Proto operator
overloads found by ADL using something like
template
struct my_complex
{
BOOST_PROTO_EXTENDS(
typename proto::terminal >::type
, my_complex
, proto::default_domain
)
};
The proto::pod_generator cl
