Re: [boost] first steps to submitting - boost :: observers

Subject: Re: [boost] first steps to submitting - boost :: observers
From: Vinnie Falco (vinnie.falco_at_[hidden])
Date: 2016-09-17 15:59:01

Robert:

Its nice to see people getting involved with the energy and desire to
contribute. Looking briefly through the materials that you provided, I
think that the addition of a few things would make your library much
more appealing and presentable:

1. Html documentation

2. Some continuous integration, e.g. Travis or CircleCI, code coverage report

3. More explanation and examples of how this might be relevant / which
use cases it addresses

There are several resources out there which help folks who want to
submit their libraries to the Boost review process. One I found is:
https://svn.boost.org/trac/boost/wiki/BestPracticeHandbook

There are also some things that you can do which will better prepare
your library for a review, they are described here:
http://www.boost.org/development/requirements.html

Hope this helps!

Vinnie

On Sat, Sep 17, 2016 at 2:10 PM, Robert McInnis <r_mcinnis_at_[hidden]> wrote:
> G'afternoon,
>
>
>
> This is my first time submitting to a public repo, please be gentle
>
>
>
> I'd like to submit a series of classes I have been using since '90.  The
> initial set implements a thread safe subject/observer pattern.  I have
> included a handful of example programs, two fairly trivial and the third
> more in-depth.  All examples are single file examples to make compilation
> trivial.
>
>
>
> This is the first re-work of my original tools, making them more
> boost-friendly.  I expect to add more default observer templates and
> observable objects, but that will come with time.
>
>
>
> WHY?
>
> --
>
> The reason for these classes is to help insure the mathematical integrity of
> your data model in relation to your business rules.  If at any time you were
> to change one of your data elements without updating all those dependent on
> it, then your data integrity would be compromised.  These classes look to
> solve that.
>
>
>
> As an example:
>
> --
>
> using namespace boost::observers ;
>
>
>
> Numeric<long> x, y, z ;
>
>
>
> //  rules:  y = x + 2;   z = y * 3 ;
>
>
>
> x = 5 ;
>
> printf( "%d \n", z ) ;
>
> x = 1 ;
>
> printf( "%d \n", z ) ;
>
> --
>
>
>
> Setting the rules properly, the classes allow for 'z' to be correct each
> time it's printed using code almost exactly like this.  This will remove the
> possibility of accidently forgetting to trigger the rule update.
>
>
>
> WHERE?
>
> --
>
> The repo can be found here:    git clone
> https://github.com/tiny/boost_observers.git
>
>
>
> Any input on how to continue from this point would also be much appreciated.
> I have skype and ventrilo servers available if that helps.
>
>
>
> Thanks in advance,
>
>
>
> Rob
>
> --
>
> Robert McInnis
>
>
>
>
>
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

-- 
Follow me on Github: https://github.com/vinniefalco