headers
Hartmut Kaiser | 1 Mar 16:28
Picon

[Review] Proto review starts today, March 1st

Hi all,

The review of Eric Nieblers Proto library starts today, March 1st 2008, and
will end on March 14th. 
I really hope to see your vote and your participation in the discussions on
the Boost mailing lists!

---------------------------------------------------

About the library:

Proto is a framework for building Domain Specific Embedded Languages in C++.
It provides tools for constructing, type-checking, transforming and
executing expression templates. More specifically, Proto provides:
 * An expression tree data structure.
 * Operator overloads for building the tree from an expression.
 * Utilities for defining the grammar to which an expression must conform.
 * An extensible mechanism for immediately executing an expression template.
 * An extensible set of tree transformations to apply to expression trees.
 * A mechanism for giving expressions additional behaviors and members.

Documentation is here:
http://boost-sandbox.sourceforge.net/libs/proto

Download proto.zip from here:
http://www.boost-consulting.com/vault/index.php?directory=Template%20Metapro
gramming

Proto is a very important infrastructure library, IHMO. It has been used as
the backbone for several other library writing efforts already, such as
(Continue reading)

Permalink | Reply |
headers
vicente.botet | 2 Mar 20:39
Picon

Re: [Parameter] is there an interest in this template parameter expresion


Hello,
First of all, sorry for the long post.

I'm doing a Locally Unique Identifier generator library.
The DSL grammar is quite complex (see below), so the use of optional
parameters seams unavoidable. I have started to use the Boost.Parameter
Library as the Boost.Flyweight does.

For the recover node which can takes two optional parameters recovery_when
and recovery_how, this results in:

<code>
template <typename Arg1=parameter::void_, typename Arg2=parameter::void_>
struct recover : on_release_marker {
private:
 typedef parameter::parameters<
     parameter::optional<
      parameter::deduced<recovery_when<> >,
      is_recovery_when<boost::mpl::_>
    >,
    parameter::optional<
     parameter::deduced<recovery_how<> >,
     is_recovery_how<boost::mpl::_>
     >
 >                                           signature;
 typedef typename signature::bind<Arg1,Arg2>::type args;
public:
 typedef typename parameter::binding<
  args,recovery_when<>,dsl::immediate<>
(Continue reading)

Permalink | Reply |
headers
vicente.botet | 5 Mar 07:26
Picon

Re: [Parameter] is there an interest in this template parameter expresion

I am really sorry, I sent my previous mail as answer to the Proto review.  I
wanted to send it a request for interest :-(.
---------------------------
Vicente Juan Botet Escriba
----- Original Message ----- 
From: "vicente.botet" <vicente.botet <at> wanadoo.fr>
To: <boost <at> lists.boost.org>
Sent: Sunday, March 02, 2008 8:39 PM
Subject: Re: [boost] [Parameter] is there an interest in this 
templateparameter expresion

>
> Hello,
> First of all, sorry for the long post.
>
> I'm doing a Locally Unique Identifier generator library.
> The DSL grammar is quite complex (see below), so the use of optional
> parameters seams unavoidable. I have started to use the Boost.Parameter
> Library as the Boost.Flyweight does.
>
> For the recover node which can takes two optional parameters recovery_when
> and recovery_how, this results in:
>
> <code>
> template <typename Arg1=parameter::void_, typename Arg2=parameter::void_>
> struct recover : on_release_marker {
> private:
> typedef parameter::parameters<
>     parameter::optional<
>      parameter::deduced<recovery_when<> >,
(Continue reading)

Permalink | Reply |
headers
Markus Werle | 3 Mar 12:02
Picon

Re: [Review] Proto review starts today, March 1st

Hartmut Kaiser <hartmut.kaiser <at> gmail.com> writes:

> 
> Hi all,
> 
> The review of Eric Nieblers Proto library starts today, March 1st 2008, and
> will end on March 14th. 

Could you be so nice to modify the main website to reflect this?
I nearly missed this event and I think others also got used to the
fact that reviews are announced on the website.

I also request more time for the review. 
Proto is way too important and too complicated (for me) to be 
reviewed in such a short time. 

Markus

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Permalink | Reply |
headers
Hartmut Kaiser | 3 Mar 15:30
Picon

Re: [Review] Proto review starts today, March 1st

> > The review of Eric Nieblers Proto library starts today, March 1st
> 2008, and
> > will end on March 14th.
> 
> Could you be so nice to modify the main website to reflect this?
> I nearly missed this event and I think others also got used to the
> fact that reviews are announced on the website.

Done. Thanks for pointing this out.

> I also request more time for the review.
> Proto is way too important and too complicated (for me) to be
> reviewed in such a short time.

Let's cross this bridge when we're there.

Regards Hartmut

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Permalink | Reply |
headers
Detlef Wilkening | 13 Mar 21:25
Picon

Re: [Review] Proto review starts today, March 1st

Hello,

here my review for Proto.

 > > - What is your evaluation of the design?
Very good. It is noticeable, that Proto has get many feedback from
different projects like Spirit 2.

 > > - What is your evaluation of the implementation?
I haven't look into the implementation.

 > > - What is your evaluation of the documentation?
 > >
I would likt to see more introduction and easy examples. And - as part
of the introduction - what I can do with Proto. What are the advantages
of usind expression templates instead of normal operator overloading?
What can I do with Proto, which is not implementable with normal
language features? Examples for transformation of expression.

I think, Eric should write a book for people like me, who is not a
beginner of C++, but not a crack who makes the whole day metaprogramming.

 > > - What is your evaluation of the potential usefulness of the library?
 > >
I think, it is very usefull, because with Proto I could implement little
helpfull utilities like Assign very easy. And it is possible to create
big DSELs like Spirit. But - I repeat myself - we need more beginner
documentation to see and use the capabilities of Proto using.

 > > - Did you try to use the library?  With what compiler?
(Continue reading)

Permalink | Reply |

Gmane