[Boost-announce] Boost.Pimpl upcoming formal review (June 15 - June 24)

Subject: [Boost-announce] Boost.Pimpl upcoming formal review (June 15 - June 24)
From: Glen Fernandes (glen.fernandes_at_[hidden])
Date: 2014-06-05 12:32:47

The formal review period of Boost.Pimpl by Vladimir Batov is scheduled
to begin later this month, on June 15th, and will conclude on June
24th, and we welcome your participation.

Vladimir's library provides a mechanism for implementing this popular,
and still very relevant, idiom. To borrow his words from the
documentation:

[quote] In the domain of commercial large-scale software development
the following design principles come to the fore:
    - component-based, modular and API-centered design,
    - separation of concerns,
    - implementation hiding,
    - minimization of compilation and component dependencies,
    - consistent and recognizable deployment and implementation patterns,
multi-platform support.

    The Pimpl idiom can help great deal achieving those goals. It is a
simple yet robust programming technique to minimize coupling via the
separation of public interface and private implementation and then
implementation hiding. [/quote]

Please feel encouraged to browse the source code, documentation, and
tests, before the review commences. Any feedback you have prior to the
review period is also very appreciated.

Source:
https://github.com/yet-another-user/boost.pimpl/

Documentation:
http://yet-another-user.github.io/boost.pimpl/

Download:
https://github.com/yet-another-user/boost.pimpl/archive/master.zip

If you would like to submit a review earlier, please provide your
thoughts on the following topics:

- What is your evaluation of the design?
- What is your evaluation of the implementation?
- What is your evaluation of the documentation?
- What is your evaluation of the potential usefulness of the library?

As well as information on the following questions:

- Did you try to use the library? With what compiler? Did you have any problems?
- How much effort did you put into your evaluation? A glance? A quick
reading? In-depth study?
- Are you knowledgeable about the problem domain?

And most importantly:

- Do you think the library should be accepted as a Boost library?

Best,
Glen