Re: [boost] Review Request: Dataflow.Signals

From: Christian Henning (chhenning_at_[hidden])
Date: 2008-03-10 23:02:45

Stjepan,

very good news! I'm glad to see that an important milestone has been
reached. This library is of great interest to me. Though, I wasted no
time to and started to play around with the library.

As a start I'm trying to get the simple example compiled which can be
found in your documentation:

http://dancinghacker.com/code/dataflow/dataflow/introduction/dataflow.html

But unfortunately including
#include <boost/dataflow/signals/component/filter.hpp>

brings my compiler to explode. Here are a list of the first few errors produced:

c:\boost_trunk\boost\fusion\mpl\clear.hpp(26) : error C2039: 'tag_of'
: is not a member of 'boost::fusion::detail'
        c:\boost_trunk\boost\fusion\mpl\clear.hpp(28) : see reference
to class template instantiation
'boost::mpl::clear_impl<boost::fusion::fusion_sequence_tag>::apply<Sequence>'
being compiled
c:\boost_trunk\boost\fusion\mpl\clear.hpp(26) : error C2146: syntax
error : missing ',' before identifier 'tag_of'
c:\boost_trunk\boost\fusion\mpl\clear.hpp(26) : error C2065: 'tag_of'
: undeclared identifier
c:\boost_trunk\boost\fusion\mpl\clear.hpp(26) : error C2976:
'boost::fusion::detail::clear' : too few template arguments
        c:\boost_trunk\boost\fusion\mpl\detail\clear.hpp(27) : see
declaration of 'boost::fusion::detail::clear'
[...]

I'm working with the boost trunk and use the MSVC compiler 7.1. I
think I remember those errors from an earlier attempt to compile the
dataflow lib. Is it my compiler or is my fusion version outdated.
Although, as I mentioned I'm working with the trunk.

Regards,
Christian

On Mon, Mar 10, 2008 at 9:25 PM, Stjepan Rajko <stipe_at_[hidden]> wrote:
> Hello,
>
>  I would like to request a formal review of the Dataflow.Signals layer
>  of the Dataflow library.   The Dataflow.Signals layer provides
>  dataflow functionality based on function calls (using Boost.Signals),
>  and is a result of the Signal Networks GSoC project from 2007.  (The
>  other layers of the Dataflow library are not quite ready, so for now
>  I'd like to keep them as implementation details and/or examples of the
>  Dataflow.Signals layer, and submit them for review at a later point.)
>
>  The documentation for the Dataflow library is located at:
>  http://dancinghacker.com/code/dataflow/
>
>  Version 0.9.0 has been uploaded to the vault, in the Dataflow directory.
>
>  There are a few more things I plan to add before the library comes up
>  for review, especially regarding the documentation and motivating
>  examples.
>
>  Description:
>
>  The Dataflow library is a generic library for dataflow programming.
>  Dataflow programs can typically be expressed as a graph in which
>  vertices represent components that process data, and edges represent
>  the flow of data between the components. As such, dataflow programs
>  can be easily reconfigured by changing the components and/or the
>  connections.
>
>  The Dataflow.Signals layer provides dataflow functionality based on
>  function calls - which is one of the fundamental ways of dataflow in
>  C++.  For its data transport mechanism, Dataflow.Signals uses
>  Boost.Signals which can be used to make lasting dataflow connections
>  based on function calls.
>
>  Dataflow.Signals provides the following to facilitate signals-based
>  dataflow networks:
>
>     * A number of useful general-purpose components, and building
>  blocks for implementing new components.
>     * Various free functions and operators for connecting and using components.
>
>  Kind regards,
>
>  Stjepan
>  _______________________________________________
>  Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
>