On 06/24/2012 01:10 AM, Eric Niebler wrote:
I've made some good progress on the C++11 proto rewrite that I'd like to
share. So far, it's been a less radical shift than I expected.
You didn't try hard enough ;)
Expressions vs. Grammars
Many new users are confused by th
on Sun Jun 24 2012, Eric Niebler
wrote:
> On 6/24/2012 4:42 PM, Dave Abrahams wrote:
>>
>> on Sun Jun 24 2012, Eric Niebler
>> wrote:
>>
>>> On 6/24/2012 8:50 AM, Irit Katriel wrote:
In the accumulators library, all the accumulators are invoked for
every update to the input.
On 6/25/2012 12:39 AM, Joel Falcou wrote:
> On 06/24/2012 01:10 AM, Eric Niebler wrote:
>>int i = LambdaEval()(_1 + 42, 0, proto::tag::data = 8);
>>
>> The 3rd parameter associates the value 8 with the data tag.
>
> How do you set up n
On 24/06/2012 01:10, Eric Niebler wrote:
As for what is not changing:
Grammars, Transforms and Algorithms
===
It would be wonderful if there were a more natural syntax for describing
proto algorithms rather than with structs, function objects, proto::or_,
proto::
On Sun, Jun 24, 2012 at 1:10 AM, Eric Niebler wrote:
> A custom transform is simply a struct that inherits from
> proto::transform and that has an operator() that accepts an arbitrary
> number of parameters.
Aha, nice! We are using the current proto to enable "custom terminals"
that also take any
On 6/25/2012 12:21 PM, Mathias Gaunard wrote:
> On 24/06/2012 01:10, Eric Niebler wrote:
>
>> As for what is not changing:
>>
>> Grammars, Transforms and Algorithms
>> ===
>> It would be wonderful if there were a more natural syntax for describing
>> proto algorithm
On 6/25/2012 12:44 PM, Bart Janssens wrote:
> On Sun, Jun 24, 2012 at 1:10 AM, Eric Niebler wrote:
>> Data parameter uses a slot mechanism
>>
>> In proto today, transforms take 3 parameters: expression, state and
>> data. As you can see from above, transforms i
