Re: Proto v4

On 04/07/08 19:43, Eric Niebler wrote:
> No library ever made it through a review unscathed and proto is no 
> exception. There's a new version of proto in branches/proto/v4,
[snip]
> These are some internal changes that probably should affect anybody:
> 
> * ref_ is no more. Children are held by plain reference, not
>    by reference wrapper.
> * s/args0/term, s/argsN/listN/
> 
I guess the removal of ref_ explains the following:
<--- cut here---
-*- mode: compilation; default-directory: 
"~/prog_dev/boost-svn/ro/branches-proto-v4/libs/proto/doc/" -*-
Compilation started at Sun Apr 13 14:44:43

bjam
warning: Graph library does not contain optional GraphML reader.
note: to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to the
note: directories containing the Expat headers and libraries, respectively.
warning: skipping optional Message Passing Interface (MPI) library.
note: to enable MPI support, add "using mpi ;" to user-config.jam.
note: to suppress this message, pass "--without-mpi" to bjam.
note: otherwise, you can safely ignore this message.
Building Boost.Regex with the optional Unicode/ICU support disabled.
Please refer to the Boost.Regex documentation for more information
(don't panic: this is a strictly optional feature).
error: Unable to find file or target named
error:     '../../../boost/proto/ref.hpp'
error: referred from project at

Re: Proto v4

On 04/07/08 19:43, Eric Niebler wrote:
> No library ever made it through a review unscathed and proto is no 
> exception. There's a new version of proto in branches/proto/v4, and 
[snip]
The attached compiles/runs with previous version; however, with
v4 I'm getting errors.  What's wrong.  The errors follow:

-*- mode: compilation; default-directory: 
"~/prog_dev/boost-svn/ro/branches-proto-v4/libs/proto/experiments3/" -*-
Compilation started at Thu Apr 17 15:07:19

bjam pass_thru_tree_req.unit-test
warning: Graph library does not contain optional GraphML reader.
note: to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to the
note: directories containing the Expat headers and libraries, respectively.
warning: skipping optional Message Passing Interface (MPI) library.
note: to enable MPI support, add "using mpi ;" to user-config.jam.
note: to suppress this message, pass "--without-mpi" to bjam.
note: otherwise, you can safely ignore this message.
Building Boost.Regex with the optional Unicode/ICU support disabled.
Please refer to the Boost.Regex documentation for more information
(don't panic: this is a strictly optional feature).
...patience...
...found 1016 targets...
...updating 3 targets...
gcc.compile.c++ 
../../../bin.v2/libs/proto/experiments3/gcc-4.1/debug/link-static/pass_thru_tree_req.o
../../../boost/utility/result_of.hpp: In instantiation of

'boost::detail::result_of_nested_result<boost::proto::op::negate<boost::proto::op::terminal<int> 

can't compile new transform protocol (was Re: Proto v4

On 04/07/08 19:43, Eric Niebler wrote:
[snip]
> Some bigger changes:
> 
> The protocol for defining a primitive transform has changed. Previously, 
> primitive transforms were just ternary function objects like this:
> 
> struct MyTransform : proto::callable
> {
[snip]
> };
> 
> You would now write this as:
> 
> struct MyTransform : proto::transform<MyTransform>
> {
>    template<class Expr, class State, class Data>
>    struct impl : proto::transform_impl<Expr, State, Data>
>    {
>      typedef ... result_type;
> 
>      result_type operator()(
>        typename impl::expr_param expr
>      , typename impl::state_param state
>      , typename impl::data_param data
>      ) const
>      {
>        return ...;
>      }
>    };

can't compile new transform protocol (was Re: Proto v4

Sorry if this is suplicate.  Tried sending to newgroup, but that
didn't show up for several minutes.

On 04/07/08 19:43, Eric Niebler wrote:
[snip]
 > Some bigger changes:
 >
 > The protocol for defining a primitive transform has changed. 
Previously, primitive transforms were just ternary function objects like 
this:
 >
 > struct MyTransform : proto::callable
 > {
[snip]
 > };
 >
 > You would now write this as:
 >
 > struct MyTransform : proto::transform<MyTransform>
 > {
 >    template<class Expr, class State, class Data>
 >    struct impl : proto::transform_impl<Expr, State, Data>
 >    {
 >      typedef ... result_type;
 >
 >      result_type operator()(
 >        typename impl::expr_param expr
 >      , typename impl::state_param state
 >      , typename impl::data_param data
 >      ) const

For diff terminals, why allow op= but disallow copy CTOR? (was Re: Proto v4

On 04/07/08 19:43, Eric Niebler wrote:
> No library ever made it through a review unscathed and proto is no 
> exception. There's a new version of proto in branches/proto/v4,
[snip]
The attached compiles showing that assignment between terminals
of different types is allowed; however, when the different
type instance comes from the CTOR, compilation fails.
That seems wrong or at least counter-intuitive.
What's the rationale for that feature?

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

_______________________________________________
Spirit-devel mailing list
Spirit-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/spirit-devel