mirror of
https://github.com/boostorg/more.git
synced 2024-12-26 23:30:29 +08:00
Move the review wizard reports to the new site. I'm not sure about how this is
organized - I would the expect the review schedule (currently in community/reviews) and reports to be together. Refs #1368. [SVN r41447]
This commit is contained in:
parent
17fdb04610
commit
4d80142e5b
@ -1,278 +0,0 @@
|
||||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||||
<meta name="generator" content="Docutils 0.3.8: http://docutils.sourceforge.net/" />
|
||||
<title>Review Wizard Status Report for April 2006</title>
|
||||
<link rel="stylesheet" href="http://www.boost.org/rst.css" type="text/css" />
|
||||
</head>
|
||||
<body>
|
||||
<div class="document" id="review-wizard-status-report-for-april-2006">
|
||||
<h1 class="title">Review Wizard Status Report for April 2006</h1>
|
||||
<div class="section" id="news">
|
||||
<h1><a name="news">News</a></h1>
|
||||
<p>April 1, 2006 -- The "Promotion Traits" Review Begins (Fast-Track)
|
||||
Proposal to add promote, integral_promotion and
|
||||
floating_point_promotion class templates to type_traits library.</p>
|
||||
<p>April 6, 2006 -- The "Function Types" Review Begins (Fast-Track)
|
||||
This library provides a metaprogramming facility
|
||||
to classify, decompose and synthesize function-, function pointer-,
|
||||
function reference- and member function pointer types.</p>
|
||||
<p>March 22, 2006 -- Asio Accepted
|
||||
Announcement: <a class="reference" href="http://lists.boost.org/Archives/boost/2006/03/102287.php">http://lists.boost.org/Archives/boost/2006/03/102287.php</a></p>
|
||||
<p>February 17, 2006 - Shared Memory Library Accepted
|
||||
Announcement: <a class="reference" href="http://lists.boost.org/boost-announce/2006/02/0083.php">http://lists.boost.org/boost-announce/2006/02/0083.php</a></p>
|
||||
<p>February 5, 2006 - Fixed String Library Rejected
|
||||
Announcement: <a class="reference" href="http://lists.boost.org/boost-announce/2006/02/0081.php">http://lists.boost.org/boost-announce/2006/02/0081.php</a></p>
|
||||
<p>We need experienced review managers. Please take a look at
|
||||
the list of libraries in need of managers and check out their
|
||||
descriptions. If you can serve as review manager for any of
|
||||
them, email Ron Garcia or Tom Brinkman "garcia at cs dot indiana dot edu"
|
||||
and "reportbase at gmail dot com" respectively.</p>
|
||||
<p>A link to this report will be posted to www.boost.org.
|
||||
If you would like us to make any modifications or additions to this
|
||||
report before we do that, please email Ron or Tom.</p>
|
||||
<p>If you're library author and plan on submitting a library for review
|
||||
in the next 3-6 months, send Ron or Tom a
|
||||
short description of your library and we'll add it to the
|
||||
Libraries Under Construction below. We know that there are many
|
||||
libaries that are near completion, but we have hard time keeping
|
||||
track all of them. Please keep us informed about your progress.</p>
|
||||
</div>
|
||||
<div class="section" id="review-queue">
|
||||
<h1><a name="review-queue">Review Queue</a></h1>
|
||||
<blockquote>
|
||||
<ul class="simple">
|
||||
<li>Promotion Traits - April 1, 2006 (fast-track)</li>
|
||||
<li>Function Types - April 6, 2006 (fast-track)</li>
|
||||
<li>Fusion</li>
|
||||
<li>Pimpl Pointer</li>
|
||||
<li>Property Tree</li>
|
||||
<li>Physical Quantities System</li>
|
||||
<li>Intrusive Containers</li>
|
||||
</ul>
|
||||
</blockquote>
|
||||
<hr class="docutils" />
|
||||
<div class="section" id="function-types-mini-re-review">
|
||||
<h2><a name="function-types-mini-re-review">Function Types (mini-re-review)</a></h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Tobias Schwinger</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Tom Brinkman</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://boost-sandbox.sourceforge.net/vault/">http://boost-sandbox.sourceforge.net/vault/</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><p class="first">This library provides a metaprogramming facility to classify,
|
||||
decompose and synthesize function-, function pointer-, function
|
||||
reference- and member function pointer types. For the purpose of
|
||||
this documentation, these types are collectively referred to as
|
||||
function types (this differs from the standard definition and
|
||||
redefines the term from a programmer's perspective to refer to
|
||||
the most common types that involve functions).</p>
|
||||
<p>The classes introduced by this library shall conform to the
|
||||
concepts of the Boost Metaprogramming library (MPL).</p>
|
||||
<dl class="docutils">
|
||||
<dt>The Function Types library enables the user to:</dt>
|
||||
<dd><ul class="first last simple">
|
||||
<li>test an arbitrary type for being a function type of specified kind,</li>
|
||||
<li>inspect properties of function types,</li>
|
||||
<li>view and modify sub types of an encapsulated function type with
|
||||
MPL Sequence operations, and</li>
|
||||
<li>synthesize function types.</li>
|
||||
</ul>
|
||||
</dd>
|
||||
</dl>
|
||||
<p class="last">This library supports variadic functions and can be configured
|
||||
to support non-default calling conventions.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section" id="promotion-traits">
|
||||
<h2><a name="promotion-traits">Promotion Traits</a></h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Alexander Nasonov</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Tobias Schwinger</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://cpp-experiment.sourceforge.net/promote-20050917.tar.gz">http://cpp-experiment.sourceforge.net/promote-20050917.tar.gz</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><p class="first">Proposal to add promote, integral_promotion and
|
||||
floating_point_promotion class templates to type_traits library.</p>
|
||||
<p>Alexander tried it on different compilers with various success:
|
||||
GNU/Linux (gentoo-hardened): gcc 3.3 and 3.4, Intel 7, 8 and 9
|
||||
Windows: VC7 free compiler
|
||||
Sparc Solaris: Sun C++ 5.3 and 5.7</p>
|
||||
<p class="last">See comments at the beginning of
|
||||
promote_enum_test.cpp for what is broken.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section" id="intrusive-containers">
|
||||
<h2><a name="intrusive-containers">Intrusive Containers</a></h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Olaf Krzikalla</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Thorsten Ottosen</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://people.freenet.de/turtle++/intrusive.zip">http://people.freenet.de/turtle++/intrusive.zip</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">While intrusive containers were and are widely used in C, they became
|
||||
more and more forgotten in the C++-world due to the presence of the
|
||||
standard containers, which don't support intrusive
|
||||
techniques. Boost.Intrusive not only reintroduces this technique to
|
||||
C++, but also encapsulates the implementation in STL-like
|
||||
interfaces. Hence anyone familiar with standard containers can use
|
||||
intrusive containers with ease.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section" id="fusion">
|
||||
<h2><a name="fusion">Fusion</a></h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Joel de Guzman</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Ron Garcia</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://spirit.sourceforge.net/dl_more/fusion_v2/">http://spirit.sourceforge.net/dl_more/fusion_v2/</a>
|
||||
<a class="reference" href="http://spirit.sourceforge.net/dl_more/fusion_v2.zip">http://spirit.sourceforge.net/dl_more/fusion_v2.zip</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><p class="first">Fusion is a library of heterogenous containers and views and
|
||||
algorithms. A set of heterogenous containers (vector, list, set and
|
||||
map) is provided out of the box along with view classes that present
|
||||
various composable views over the data. The containers and views
|
||||
follow a common sequence concept with an underlying iterator concept
|
||||
that binds it all together, suitably making the algorithms fully
|
||||
generic over all sequence types.</p>
|
||||
<p class="last">The architecture is somewhat modeled after MPL which in turn is
|
||||
modeled after STL. It is code-named "fusion" because the library is
|
||||
the "fusion" of compile time metaprogramming with runtime programming.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section" id="pimpl-pointer">
|
||||
<h2><a name="pimpl-pointer">Pimpl Pointer</a></h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Asger Mangaard</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Need Volunteer</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body">Boost Sandbox (<a class="reference" href="http://boost-consulting.com/vault/">http://boost-consulting.com/vault/</a>) under pimpl_ptr.</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">The pimpl idiom is widely used to reduce compile times and disable
|
||||
code coupling. It does so by moving private parts of a class from the
|
||||
.hpp file to the .cpp file.
|
||||
However, it's implementation can be tricky, and with many pitfalls
|
||||
(especially regarding memory management).
|
||||
The pimpl_ptr library is a single header file, implementing a special
|
||||
policy based smart pointer to greately ease the implementation of the
|
||||
pimpl idiom.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section" id="property-tree">
|
||||
<h2><a name="property-tree">Property Tree</a></h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Marcin Kalicinski</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Need Volunteer</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body">Boost Sandbox Vault - property_tree_rev4.zip
|
||||
<a class="reference" href="http://kaalus.atspace.com/ptree">http://kaalus.atspace.com/ptree</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">Property tree is a data structure - a tree of (key, value)
|
||||
pairs. It differs from its cousin, "usual" property map, because
|
||||
it is hierarchical, not linear. Thus, it is more like a
|
||||
minimalistic Document Object Model, but not bound to any
|
||||
specific file format. It can store contents of XML files,
|
||||
windows registry, JSON files, INI files, even command line
|
||||
parameters. The library contains parsers for all these formats,
|
||||
and more.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section" id="physical-quantities-system">
|
||||
<h2><a name="physical-quantities-system">Physical Quantities System</a></h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Andy Little</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Need Volunteer</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://tinyurl.com/7m5l8">http://tinyurl.com/7m5l8</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">PQS (Physical Quantities System) is used for modelling
|
||||
physical-quantities in C++ programs. The advantages over using
|
||||
built-in types in the role include: trapping errors in
|
||||
dimensional analysis, detailed semantic specifications for
|
||||
reliable and repeatable conversions between units and
|
||||
self-documentation of source code. PQS is based around the
|
||||
principles and guidelines of the International System of Units
|
||||
(SI). The library predefines a large number of quantities,
|
||||
physical and maths constants using a common syntax. The library
|
||||
also includes (or will soon include) classes for manipulating
|
||||
quantities algebraically, for example angles (radians,
|
||||
steradians, degrees,minutes,seconds) and vectors, matrices and
|
||||
quaternions for more advanced modelling of physical systems.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="libraries-under-development">
|
||||
<h1><a name="libraries-under-development">Libraries under development</a></h1>
|
||||
<p>Geometry Library - Author - Andy Little (?)</p>
|
||||
<p>C2_functions Library - Author - Marcus Mendenhall</p>
|
||||
<p>Please let us know of any libraries you are currently
|
||||
developing that you intend to submit for review.</p>
|
||||
</div>
|
||||
</div>
|
||||
<hr class="docutils footer" />
|
||||
<div class="footer">
|
||||
Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source.
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
@ -1,325 +0,0 @@
|
||||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||||
<meta name="generator" content="Docutils 0.5: http://docutils.sourceforge.net/" />
|
||||
<title>Review Wizard Status Report for January 2006</title>
|
||||
<link rel="stylesheet" href="http://www.boost.org/rst.css" type="text/css" />
|
||||
</head>
|
||||
<body>
|
||||
<div class="document" id="review-wizard-status-report-for-january-2006">
|
||||
<h1 class="title">Review Wizard Status Report for January 2006</h1>
|
||||
<div class="section">
|
||||
<h1><a id="news" name="news">News</a></h1>
|
||||
<p>Happy New Year! Here are some statistics regarding Boost Library
|
||||
reviews in 2005:</p>
|
||||
<blockquote>
|
||||
<ul class="simple">
|
||||
<li>12 Libraries were reviewed</li>
|
||||
<li>8 Libraries were accepted</li>
|
||||
<li>1 Library (Function Types) was accepted pending a mini-review</li>
|
||||
<li>2 Libraries were rejected</li>
|
||||
<li>1 Library has yet to receive a final verdict (ASIO)</li>
|
||||
</ul>
|
||||
</blockquote>
|
||||
<p>Policy Pointer has been removed from the review queue because the author has
|
||||
stated that it is not quite ready.</p>
|
||||
<p>We need review managers. Please take a look at the list of libraries
|
||||
in need of managers and check out their descriptions. If you can
|
||||
serve as review manager for any of them, send one of us an email.</p>
|
||||
<dl class="docutils">
|
||||
<dt>Note:</dt>
|
||||
<dd>If you have any suggestions about how we could improve
|
||||
the Review Wizard's status report,
|
||||
please email "reportbase at gmail dot com"
|
||||
and "garcia at cs dot indiana dot edu".</dd>
|
||||
</dl>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h1><a id="review-managers-needed" name="review-managers-needed">Review Managers Needed</a></h1>
|
||||
<p>There are a few libraries in the review queue in need
|
||||
of review managers. If you would like to volunteer to be a review
|
||||
manager, please contact Ron or Tom.</p>
|
||||
<p>The following libraries still require review managers:</p>
|
||||
<blockquote>
|
||||
<ul class="simple">
|
||||
<li>Fusion</li>
|
||||
<li>Shmem</li>
|
||||
<li>Pimpl Pointer</li>
|
||||
<li>Type Traits (modification)</li>
|
||||
<li>Function Types</li>
|
||||
</ul>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h1><a id="review-queue" name="review-queue">Review Queue</a></h1>
|
||||
<blockquote>
|
||||
<ul class="simple">
|
||||
<li>Fixed Strings - January 19 2006 - January 28 2006</li>
|
||||
<li>Intrusive Containers</li>
|
||||
<li>Function Types (mini-re-review)</li>
|
||||
<li>Shmem</li>
|
||||
<li>Fusion</li>
|
||||
<li>Pimpl Pointer</li>
|
||||
<li>Type Traits (modification)</li>
|
||||
</ul>
|
||||
</blockquote>
|
||||
<hr class="docutils" />
|
||||
<div class="section">
|
||||
<h2><a id="fixed-strings" name="fixed-strings">Fixed Strings</a></h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Reece Dunn</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Harmut Kaiser</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body">Boost Sandbox (<a class="reference" href="http://boost-sandbox.sourceforge.net/">http://boost-sandbox.sourceforge.net/</a>) under fixed_string</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">The fixed string library provides buffer overrun protection for static
|
||||
sized strings (char s[ n ]). It provides a C-style string
|
||||
interface for compatibility with C code (for
|
||||
example, porting a C program to C++).
|
||||
There is also a std::string-style interface using a class based on
|
||||
flex_string by Andre Alexandrescu with a few limitations due to the
|
||||
non-resizable nature of the class.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a id="intrusive-containers" name="intrusive-containers">Intrusive Containers</a></h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Olaf Krzikalla</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">to be determined</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://people.freenet.de/turtle++/intrusive.zip">http://people.freenet.de/turtle++/intrusive.zip</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">While intrusive containers were and are widely used in C, they became
|
||||
more and more forgotten in the C++-world due to the presence of the
|
||||
standard containers, which don't support intrusive
|
||||
techniques. Boost.Intrusive not only reintroduces this technique to
|
||||
C++, but also encapsulates the implementation in STL-like
|
||||
interfaces. Hence anyone familiar with standard containers can use
|
||||
intrusive containers with ease.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a id="function-types-mini-re-review" name="function-types-mini-re-review">Function Types (mini-re-review)</a></h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body"><p class="first">Tobias Schwinger</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body"><p class="first">to be determined</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><p class="first"><a class="reference" href="http://boost-sandbox.sourceforge.net/vault/">http://boost-sandbox.sourceforge.net/vault/</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><dl class="first last docutils">
|
||||
<dt>This library provides a metaprogramming facility</dt>
|
||||
<dd><p class="first last">to classify, decompose and synthesize function-,
|
||||
function pointer-, function reference- and
|
||||
member function pointer types. For the purpose
|
||||
of this documentation, these types are
|
||||
collectively referred to as function
|
||||
types (this differs from the standard
|
||||
definition and redefines the term from
|
||||
a programmer's perspective to refer to
|
||||
the most common types that involve functions).</p>
|
||||
</dd>
|
||||
<dt>The classes introduced by this library</dt>
|
||||
<dd><p class="first last">shall conform to the concepts of the
|
||||
Boost Metaprogramming library (MPL).</p>
|
||||
</dd>
|
||||
<dt>The Function Types library enables the user to:</dt>
|
||||
<dd><ul class="first last simple">
|
||||
<li>test an arbitrary type for
|
||||
being a function type of specified kind,</li>
|
||||
<li>inspect properties of function types,</li>
|
||||
<li>view and modify sub types of an
|
||||
encapsulated function type with
|
||||
MPL Sequence operations, and</li>
|
||||
<li>synthesize function types.</li>
|
||||
</ul>
|
||||
</dd>
|
||||
<dt>This library supports variadic functions and</dt>
|
||||
<dd><p class="first last">can be configured to support
|
||||
non-default calling conventions.</p>
|
||||
</dd>
|
||||
</dl>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a id="shmem" name="shmem">Shmem</a></h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body"><p class="first">Ion Gaztanaga</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body"><p class="first">to be determined</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><p class="first">Boost Sandbox Vault -> Memory (<a class="reference" href="http://boost-sandbox.sourceforge.net/vault/index.php?direction=0&order=&directory=Memory">http://boost-sandbox.sourceforge.net/vault/index.php?direction=0&order=&directory=Memory</a>)</p>
|
||||
<p><a class="reference" href="http://ice.prohosting.com/newfunk/boost/libs/shmem/doc/html/index.html">http://ice.prohosting.com/newfunk/boost/libs/shmem/doc/html/index.html</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><p class="first">Shmem offers tools to simplify shared memory usage in
|
||||
applications. These include shared memory creation/destruction and
|
||||
synchronization objects. It also implements dynamic allocation of
|
||||
portions of a shared memory segment and an easy way to construct C++
|
||||
objects in shared memory.</p>
|
||||
<p class="last">Apart from this, Shmem implements a wide range of STL-like containers
|
||||
and allocators that can be safely placed in shared memory, helpful to
|
||||
implement complex shared memory data-bases and other efficient
|
||||
inter-process communications.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a id="fusion" name="fusion">Fusion</a></h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body"><p class="first">Joel de Guzman</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body"><p class="first">to be determined</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><p class="first"><a class="reference" href="http://spirit.sourceforge.net/dl_more/fusion_v2/">http://spirit.sourceforge.net/dl_more/fusion_v2/</a>
|
||||
<a class="reference" href="http://spirit.sourceforge.net/dl_more/fusion_v2.zip">http://spirit.sourceforge.net/dl_more/fusion_v2.zip</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><p class="first">Fusion is a library of heterogenous containers and views and
|
||||
algorithms. A set of heterogenous containers (vector, list, set and
|
||||
map) is provided out of the box along with view classes that present
|
||||
various composable views over the data. The containers and views
|
||||
follow a common sequence concept with an underlying iterator concept
|
||||
that binds it all together, suitably making the algorithms fully
|
||||
generic over all sequence types.</p>
|
||||
<p class="last">The architecture is somewhat modeled after MPL which in turn is
|
||||
modeled after STL. It is code-named "fusion" because the library is
|
||||
the "fusion" of compile time metaprogramming with runtime programming.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a id="pimpl-pointer" name="pimpl-pointer">Pimpl Pointer</a></h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Asger Mangaard</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">to be determined</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body">Boost Sandbox (<a class="reference" href="http://boost-consulting.com/vault/">http://boost-consulting.com/vault/</a>) under pimpl_ptr.</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">The pimpl idiom is widely used to reduce compile times and disable
|
||||
code coupling. It does so by moving private parts of a class from the
|
||||
.hpp file to the .cpp file.
|
||||
However, it's implementation can be tricky, and with many pitfalls
|
||||
(especially regarding memory management).
|
||||
The pimpl_ptr library is a single header file, implementing a special
|
||||
policy based smart pointer to greately ease the implementation of the
|
||||
pimpl idiom.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h2><a id="type-traits-modification" name="type-traits-modification">Type_Traits (modification)</a></h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body"><p class="first">Alexander Nasonov</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body"><p class="first">to be determined</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><p class="first"><a class="reference" href="http://cpp-experiment.sourceforge.net/promote-20050917.tar.gz">http://cpp-experiment.sourceforge.net/promote-20050917.tar.gz</a>
|
||||
or <a class="reference" href="http://cpp-experiment.sourceforge.net/promote-20050917/">http://cpp-experiment.sourceforge.net/promote-20050917/</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><p class="first">Proposal to add promote, integral_promotion and
|
||||
floating_point_promotion class templates to type_traits library.</p>
|
||||
<p>Alexander tried it on different compilers with various success:
|
||||
GNU/Linux (gentoo-hardened): gcc 3.3 and 3.4, Intel 7, 8 and 9
|
||||
Windows: VC7 free compiler
|
||||
Sparc Solaris: Sun C++ 5.3 and 5.7</p>
|
||||
<p>See comments at the beginning of promote_enum_test.cpp for what is broken.
|
||||
<a class="reference" href="http://cpp-experiment.sourceforge.net/promote-20050917/libs/type_traits/test/promote_enum_test.cpp">http://cpp-experiment.sourceforge.net/promote-20050917/libs/type_traits/test/promote_enum_test.cpp</a></p>
|
||||
<p class="last">Alexander requests a fast-track review.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section">
|
||||
<h1><a id="libraries-under-development" name="libraries-under-development">Libraries under development</a></h1>
|
||||
<div class="section">
|
||||
<h2><a id="property-tree" name="property-tree">Property Tree</a></h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Marcin Kalicinski</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body">Boost Sandbox Vault (<a class="reference" href="http://boost-consulting.com/vault/">http://boost-consulting.com/vault/</a>)
|
||||
property_tree_rev3.zip</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
<p>Please let us know of any libraries you are currently
|
||||
developing that you intend to submit for review.</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="footer">
|
||||
<hr class="footer" />
|
||||
Generated on: 2006-01-20 17:42 UTC.
|
||||
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
@ -1,423 +0,0 @@
|
||||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||||
<meta name="generator" content="Docutils 0.3.8: http://docutils.sourceforge.net/" />
|
||||
<title>Review Wizard Status Report for November 2007</title>
|
||||
<link rel="stylesheet" href="http://boost.org/rst.css" type="text/css" />
|
||||
</head>
|
||||
<body>
|
||||
<div class="document" id="review-wizard-status-report-for-november-2007">
|
||||
<h1 class="title">Review Wizard Status Report for November 2007</h1>
|
||||
<div class="section" id="news">
|
||||
<h1><a name="news">News</a></h1>
|
||||
<dl class="docutils">
|
||||
<dt>November 7, 2007 - Exception Library Accepted</dt>
|
||||
<dd>Announcement: <a class="reference" href="http://lists.boost.org/boost-users/2007/11/31912.php">http://lists.boost.org/boost-users/2007/11/31912.php</a></dd>
|
||||
</dl>
|
||||
<p>We need experienced review managers. Please take a look at the list
|
||||
of libraries in need of managers and check out their descriptions. In
|
||||
general review managers are active boost participants or library
|
||||
contributors. If you can serve as review manager for any of them,
|
||||
email Ron Garcia or John Phillips, "garcia at cs dot indiana dot edu"
|
||||
and "jphillip at capital dot edu" respectively.</p>
|
||||
<p>A link to this report will be posted to www.boost.org.
|
||||
If you would like us to make any modifications or additions to this
|
||||
report before we do that, please email Ron or John.</p>
|
||||
<p>If you're library author and plan on submitting a library for review
|
||||
in the next 3-6 months, send Ron or John a short description of your
|
||||
library and we'll add it to the Libraries Under Construction below.
|
||||
We know that there are many libraries that are near completion, but we
|
||||
have hard time keeping track all of them. Please keep us informed
|
||||
about your progress.</p>
|
||||
</div>
|
||||
<div class="section" id="review-queue">
|
||||
<h1><a name="review-queue">Review Queue</a></h1>
|
||||
<ul class="simple">
|
||||
<li>Finite State Machines</li>
|
||||
<li>Floating Point Utilities</li>
|
||||
<li>Switch</li>
|
||||
<li>Property Map (fast-track)</li>
|
||||
<li>Graph (fast-track)</li>
|
||||
<li>Forward (fast-track)</li>
|
||||
<li>Singleton (fast-track)</li>
|
||||
<li>Factory (fast-track)</li>
|
||||
<li>Lexer</li>
|
||||
<li>Thread-Safe Signals</li>
|
||||
<li>Logging</li>
|
||||
<li>Flyweight</li>
|
||||
<li>Unordered Containers</li>
|
||||
</ul>
|
||||
<hr class="docutils" />
|
||||
<div class="section" id="finite-state-machines">
|
||||
<h2><a name="finite-state-machines">Finite State Machines</a></h2>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Andrey Semashev</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Martin Vuille</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://tinyurl.com/yjozfn">Boost Sandbox Vault</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><p class="first">The Boost.FSM library is an implementation of FSM (stands for
|
||||
Finite State Machine) programming concept. The main goals of the
|
||||
library are:</p>
|
||||
<ul class="last simple">
|
||||
<li>Simplicity. It should be very simple to create state machines using
|
||||
this library.</li>
|
||||
<li>Performance. The state machine infrastructure should not be
|
||||
very time and memory-consuming in order to be applicable in
|
||||
more use cases.</li>
|
||||
<li>Extensibility. A developer may want to add more states to an
|
||||
existing state machine. A developer should also be able to
|
||||
specify additional transitions and events for the machine with
|
||||
minimum modifications to the existing code.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<div class="section" id="floating-point-utilities">
|
||||
<h2><a name="floating-point-utilities">Floating Point Utilities</a></h2>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Johan Råde</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Need Volunteer</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://boost-consulting.com/vault/index.php?directory=Math%20-%20Numerics">Boost Sandbox Vault</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><p class="first">The Floating Point Utilities library contains the following:</p>
|
||||
<ul class="last simple">
|
||||
<li>Floating point number classification functions: fpclassify, isfinite,
|
||||
isinf, isnan, isnormal (Follows TR1)</li>
|
||||
<li>Sign bit functions: signbit, copysign, changesign (Follows TR1)</li>
|
||||
<li>Facets that format and parse infinity and NaN according to the C99
|
||||
standard (These can be used for portable handling of infinity and NaN
|
||||
in text streams).</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<div class="section" id="switch">
|
||||
<h2><a name="switch">Switch</a></h2>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Steven Watanabe</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Need Volunteer</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://boost-consulting.com/vault/index.php?action=downloadfile&filename=mcs_units_v0.7.1.zip&directory=Units">Boost Sandbox Vault</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">The built in C/C++ switch statement is very efficient. Unfortunately,
|
||||
unlike a chained if/else construct there is no easy way to use it when
|
||||
the number of cases depends on a template parameter. The Switch library
|
||||
addresses this issue.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<div class="section" id="property-map-fast-track">
|
||||
<h2><a name="property-map-fast-track">Property Map (fast-track)</a></h2>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Andrew Sutton</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Jeremy Siek</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://svn.boost.org/svn/boost/sandbox/graph-v2">http://svn.boost.org/svn/boost/sandbox/graph-v2</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><p class="first">A number of additions and modifications to the Property Map Library,
|
||||
including:</p>
|
||||
<ul class="last simple">
|
||||
<li>A constant-valued property map, useful for naturally unweighted
|
||||
graphs.</li>
|
||||
<li>A noop-writing property map, useful when you have to provide an
|
||||
argument, but just don't care about the output.</li>
|
||||
<li>See
|
||||
<a class="reference" href="http://svn.boost.org/trac/boost/browser/sandbox/graph-v2/libs/property_map/ChangeLog">ChangeLog</a>
|
||||
for details.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<div class="section" id="graph-fast-track">
|
||||
<h2><a name="graph-fast-track">Graph (fast-track)</a></h2>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Andrew Sutton</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Jeremy Siek</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://svn.boost.org/svn/boost/sandbox/graph-v2">http://svn.boost.org/svn/boost/sandbox/graph-v2</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><p class="first">A number of additions and modifications to the Graph Library,
|
||||
including:</p>
|
||||
<ul class="last simple">
|
||||
<li>Two new graph classes (undirected and directed) which are intended
|
||||
to make the library more approachable for new developers</li>
|
||||
<li>A suite of graph measures including degree and closeness
|
||||
centrality, mean geodesic distance, eccentricity, and clustering
|
||||
coefficients.</li>
|
||||
<li>An algorithm for visiting all cycles in a directed graph (Tiernan's
|
||||
from 1970ish). It works for undirected graphs too, but reports cycles
|
||||
twice (one for each direction).</li>
|
||||
<li>An algorithm for visiting all the cliques a graph (Bron&Kerbosch).
|
||||
Works for both directed and undirected.</li>
|
||||
<li>Derived graph measures radius and diameter (from eccentricity) and
|
||||
girth and circumference (from Tiernan), and clique number (from
|
||||
Bron&Kerbosch).</li>
|
||||
<li>An exterior_property class that helps hides some of the weirdness
|
||||
with exterior properties.</li>
|
||||
<li>runtime and compile-time tests for the new algorithms.</li>
|
||||
<li>a substantial amount of documentation</li>
|
||||
<li>Graph cores, implemented by David Gleich (@Stanford University)</li>
|
||||
<li>Deterministic graph generators - capable of creating or inducing
|
||||
specific types of graphs over a vertex set (e.g., star graph, wheel
|
||||
graph, prism graph, etc). There are several other specific types that
|
||||
could be added to this, but I haven't had the time just yet.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<div class="section" id="forward-fast-track">
|
||||
<h2><a name="forward-fast-track">Forward (fast-track)</a></h2>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Tobias Schwinger</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">John Torjo</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://boost-consulting.com/vault/index.php?&direction=0&order=&directory=X-Files">http://boost-consulting.com/vault/index.php?&direction=0&order=&directory=X-Files</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">A brute-force solution to the forwarding problem.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<div class="section" id="singleton-fast-track">
|
||||
<h2><a name="singleton-fast-track">Singleton (fast-track)</a></h2>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Tobias Schwinger</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">John Torjo</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://boost-consulting.com/vault/index.php?&direction=0&order=&directory=X-Files">http://boost-consulting.com/vault/index.php?&direction=0&order=&directory=X-Files</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">Three thread-safe Singleton templates with an
|
||||
easy-to-use interface.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<div class="section" id="factory-fast-track">
|
||||
<h2><a name="factory-fast-track">Factory (fast-track)</a></h2>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Tobias Schwinger</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">John Torjo</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://boost-consulting.com/vault/index.php?&direction=0&order=&directory=X-Files">http://boost-consulting.com/vault/index.php?&direction=0&order=&directory=X-Files</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">Generic factories.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<div class="section" id="lexer">
|
||||
<h2><a name="lexer">Lexer</a></h2>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Ben Hanson</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Need Volunteer</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://boost-consulting.com/vault/index.php?action=downloadfile&filename=boost.lexer.zip&directory=Strings%20">http://boost-consulting.com/vault/index.php?action=downloadfile&filename=boost.lexer.zip&directory=Strings%20</a>-%20Text%20Processing&</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">A programmable lexical analyser generator inspired by 'flex'.
|
||||
Like flex, it is programmed by the use of regular expressions
|
||||
and outputs a state machine as a number of DFAs utilising
|
||||
equivalence classes for compression.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<div class="section" id="thread-safe-signals">
|
||||
<h2><a name="thread-safe-signals">Thread-Safe Signals</a></h2>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Frank Hess</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Need Volunteer</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://www.boost-consulting.com/vault/index.php?&direction=0&order=&directory=thread_safe_signals">http://www.boost-consulting.com/vault/index.php?&direction=0&order=&directory=thread_safe_signals</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">A thread-safe implementation of Boost.signals that
|
||||
has some interface changes to accommodate thread safety, mostly with
|
||||
respect to automatic connection management.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<div class="section" id="logging">
|
||||
<h2><a name="logging">Logging</a></h2>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">John Torjo</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Need Volunteer</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://torjo.com/log2/">http://torjo.com/log2/</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">Used properly, logging is a very powerful tool. Besides aiding
|
||||
debugging/testing, it can also show you how your application is
|
||||
used. The Boost Logging Library allows just for that, supporting
|
||||
a lot of scenarios, ranging from very simple (dumping all to one
|
||||
destination), to very complex (multiple logs, some enabled/some
|
||||
not, levels, etc). It features a very simple and flexible
|
||||
interface, efficient filtering of messages, thread-safety,
|
||||
formatters and destinations, easy manipulation of logs, finding
|
||||
the best logger/filter classes based on your application's
|
||||
needs, you can define your own macros and much more!</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<div class="section" id="flyweight">
|
||||
<h2><a name="flyweight">Flyweight</a></h2>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Joaquín M López Muñoz</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Need Volunteer</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://www.boost-consulting.com/vault/index.php?action=downloadfile&filename=flyweight.zip&directory=Patterns">http://www.boost-consulting.com/vault/index.php?action=downloadfile&filename=flyweight.zip&directory=Patterns</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">Flyweights are small-sized handle classes granting
|
||||
constant access to shared common data, thus allowing for the
|
||||
management of large amounts of entities within reasonable memory
|
||||
limits. Boost.Flyweight makes it easy to use this common
|
||||
programming idiom by providing the class template flyweight<T>,
|
||||
which acts as a drop-in replacement for const T.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<div class="section" id="unordered-containers">
|
||||
<h2><a name="unordered-containers">Unordered Containers</a></h2>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Daniel James</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Need Volunteer</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference" href="http://www.boost-consulting.com/vault/index.php?action=downloadfile&filename=unordered.zip&directory=Containers">http://www.boost-consulting.com/vault/index.php?action=downloadfile&filename=unordered.zip&directory=Containers</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">An implementation of the unordered containers specified
|
||||
in TR1, with most of the changes from the recent draft standards.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="libraries-under-development">
|
||||
<h1><a name="libraries-under-development">Libraries under development</a></h1>
|
||||
<div class="section" id="dataflow">
|
||||
<h2><a name="dataflow">Dataflow</a></h2>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Stjepan Rajko</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">The Dataflow library provides generic support for data
|
||||
producers, consumers, and connections between the two. It also
|
||||
provides layers for several specific dataflow mechanisms, namely
|
||||
Boost.Signals, VTK data/display pipelines, and plain
|
||||
pointers. The Dataflow library came out of the Signal Network
|
||||
GSoC project, mentored by Doug Gregor.</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Status:</th><td class="field-body">I am polishing the Dataflow library for submission, and am expecting
|
||||
to add it to the review queue in the next couple of months.
|
||||
I am currently ironing out some faults in the design of the library,
|
||||
filling in missing features, and testing it on / adapting it to
|
||||
different dataflow mechanisms (currently VTK and soon
|
||||
Boost.Iostreams). As soon as I'm pretty sure that things are going
|
||||
the right way, I'll submit this to the review queue while I do the
|
||||
finishing touches.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<div class="section" id="constrained-value">
|
||||
<h2><a name="constrained-value">Constrained Value</a></h2>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Robert Kawulak</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><p class="first"><a class="reference" href="http://rk.go.pl/f/constrained_value.zip">http://rk.go.pl/f/constrained_value.zip</a></p>
|
||||
<p class="last"><a class="reference" href="http://rk.go.pl/r/constrained_value">http://rk.go.pl/r/constrained_value</a> (Documentation)</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">The Constrained Value library contains class templates
|
||||
useful for creating constrained objects. The simplest example
|
||||
of a constrained object is hour. The only valid values for an hour
|
||||
within a day are integers from the range [0, 23]. With this library,
|
||||
you can create a variable which behaves exactly like int, but does
|
||||
not allow for assignment of values which do not belong to the
|
||||
allowed range. The library doesn't focus only on constrained
|
||||
objects that hold a value belonging to a specified range (i.e.,
|
||||
bounded objects). Virtually any constraint can be imposed using
|
||||
appropriate predicate. You can specify what happens in case of
|
||||
assignment of an invalid value, e.g. an exception may be thrown or
|
||||
the value may be adjusted to meet the constraint criterions.</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Status:</th><td class="field-body">I'm planning to finish it in 1-2 months.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>Please let us know of any libraries you are currently
|
||||
developing that you intend to submit for review.</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
@ -1,329 +0,0 @@
|
||||
<?xml version="1.0" encoding="utf-8" ?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||||
<meta name="generator" content="Docutils 0.5: http://docutils.sourceforge.net/" />
|
||||
<title>Review Wizard Status Report for September 2007</title>
|
||||
<link rel="stylesheet" href="http://boost.org/rst.css" type="text/css" />
|
||||
</head>
|
||||
<body>
|
||||
<div class="document" id="review-wizard-status-report-for-september-2007">
|
||||
<h1 class="title">Review Wizard Status Report for September 2007</h1>
|
||||
|
||||
<div class="section" id="news">
|
||||
<h1>News</h1>
|
||||
<dl class="docutils">
|
||||
<dt>August 17, 2007 -- Time Series Accepted.</dt>
|
||||
<dd>Announcement: <a class="reference external" href="http://lists.boost.org/boost-announce/2007/08/0142.php">http://lists.boost.org/boost-announce/2007/08/0142.php</a></dd>
|
||||
<dt>July 24, 2007 -- Boost Version 1.34.1 Released.</dt>
|
||||
<dd>This is a bug fix release addressing many problems with the 1.34.0 release.
|
||||
Announcement: <a class="reference external" href="http://svn.boost.org/trac/boost/query?status=closed&milestone=Boost+1.34.1">http://svn.boost.org/trac/boost/query?status=closed&milestone=Boost+1.34.1</a></dd>
|
||||
</dl>
|
||||
<p>We need experienced review managers. Please take a look at the list
|
||||
of libraries in need of managers and check out their descriptions. In
|
||||
general review managers are active boost participants or library
|
||||
contributors. If you can serve as review manager for any of them,
|
||||
email Ron Garcia or John Phillips, "garcia at cs dot indiana dot edu"
|
||||
and "jphillip at capital dot edu" respectively.</p>
|
||||
<p>A link to this report will be posted to www.boost.org.
|
||||
If you would like us to make any modifications or additions to this
|
||||
report before we do that, please email Ron or John.</p>
|
||||
<p>If you're library author and plan on submitting a library for review
|
||||
in the next 3-6 months, send Ron or John a short description of your
|
||||
library and we'll add it to the Libraries Under Construction below.
|
||||
We know that there are many libraries that are near completion, but we
|
||||
have hard time keeping track all of them. Please keep us informed
|
||||
about your progress.</p>
|
||||
</div>
|
||||
<div class="section" id="review-queue">
|
||||
<h1>Review Queue</h1>
|
||||
<blockquote>
|
||||
<ul class="simple">
|
||||
<li>Exception</li>
|
||||
<li>Finite State Machines</li>
|
||||
<li>Floating Point Utilities</li>
|
||||
<li>Switch</li>
|
||||
<li>Property Map (fast-track)</li>
|
||||
<li>Graph (fast-track)</li>
|
||||
</ul>
|
||||
</blockquote>
|
||||
<hr class="docutils" />
|
||||
<div class="section" id="exception">
|
||||
<h2>Exception</h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body"><p class="first">Emil Dotchevski</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body"><p class="first">Need Volunteer</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><p class="first"><a class="reference external" href="http://www.revergestudios.com/boost-exception/boost-exception.zip">http://www.revergestudios.com/boost-exception/boost-exception.zip</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><p class="first">The purpose of this library is to free designers of
|
||||
exception classes from having to consider what data needs to be
|
||||
stored in exception objects in order for the catch site to be
|
||||
able to make sense of what went wrong.</p>
|
||||
<p class="last">When the exception class is used, arbitrary values can be stored
|
||||
in any exception. This can be done directly in the
|
||||
throw-expression, or at a later time as the exception object
|
||||
propagates up the call stack. The ability to add data to any
|
||||
exception object after it has been thrown is important, because
|
||||
often some of the information needed to handle an exception is
|
||||
unavailable at the time of the throw.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section" id="finite-state-machines">
|
||||
<h2>Finite State Machines</h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body"><p class="first">Andrey Semashev</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body"><p class="first">Martin Vuille</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><p class="first"><a class="reference external" href="http://tinyurl.com/yjozfn">Boost Sandbox Vault</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><p class="first">The Boost.FSM library is an implementation of FSM (stands for
|
||||
Finite State Machine) programming concept. The main goals of the
|
||||
library are:</p>
|
||||
<ul class="last simple">
|
||||
<li>Simplicity. It should be very simple to create state machines using
|
||||
this library.</li>
|
||||
<li>Performance. The state machine infrastructure should not be
|
||||
very time and memory-consuming in order to be applicable in
|
||||
more use cases.</li>
|
||||
<li>Extensibility. A developer may want to add more states to an
|
||||
existing state machine. A developer should also be able to
|
||||
specify additional transitions and events for the machine with
|
||||
minimum modifications to the existing code.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section" id="floating-point-utilities">
|
||||
<h2>Floating Point Utilities</h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body"><p class="first">Johan RÂde</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body"><p class="first">Need Volunteer</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><p class="first"><a class="reference external" href="http://boost-consulting.com/vault/index.php?directory=Math%20-%20Numerics">Boost Sandbox Vault</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><p class="first">The Floating Point Utilities library contains the following:</p>
|
||||
<ul class="last simple">
|
||||
<li>Floating point number classification functions: fpclassify, isfinite,
|
||||
isinf, isnan, isnormal (Follows TR1)</li>
|
||||
<li>Sign bit functions: signbit, copysign, changesign (Follows TR1)</li>
|
||||
<li>Facets that format and parse infinity and NaN according to the C99
|
||||
standard. (These can be used for portable handling of infinity and NaN
|
||||
in text streams.)</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section" id="switch">
|
||||
<h2>Switch</h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Steven Watanabe</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body">Need Volunteer</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><a class="reference external" href="http://boost-consulting.com/vault/index.php?action=downloadfile&filename=mcs_units_v0.7.1.zip&directory=Units">Boost Sandbox Vault</a></td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">The built in C/C++ switch statement is very efficient. Unfortunately,
|
||||
unlike a chained if/else construct there is no easy way to use it when
|
||||
the number of cases depends on a template parameter. The Switch library
|
||||
addresses this issue.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section" id="property-map-fast-track">
|
||||
<h2>Property Map (fast-track)</h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body"><p class="first">Andrew Sutton</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body"><p class="first">Jeremy Siek</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><p class="first"><a class="reference external" href="http://svn.boost.org/svn/boost/sandbox/graph-v2">http://svn.boost.org/svn/boost/sandbox/graph-v2</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><p class="first">A number of additions and modifications to the Property Map Library,
|
||||
including:</p>
|
||||
<blockquote class="last">
|
||||
<ul class="simple">
|
||||
<li>A constant-valued property map, useful for naturally unweighted
|
||||
graphs.</li>
|
||||
<li>A noop-writing property map, useful when you have to provide an
|
||||
argument, but just don't care about the output.</li>
|
||||
<li>See
|
||||
<a class="reference external" href="http://svn.boost.org/trac/boost/browser/sandbox/graph-v2/libs/property_map/ChangeLog">ChangeLog</a>
|
||||
for details.</li>
|
||||
</ul>
|
||||
</blockquote>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section" id="graph-fast-track">
|
||||
<h2>Graph (fast-track)</h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body"><p class="first">Andrew Sutton</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Review Manager:</th><td class="field-body"><p class="first">Jeremy Siek</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><p class="first"><a class="reference external" href="http://svn.boost.org/svn/boost/sandbox/graph-v2">http://svn.boost.org/svn/boost/sandbox/graph-v2</a></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><p class="first">A number of additions and modifications to the Graph Library,
|
||||
including:</p>
|
||||
<ul class="last simple">
|
||||
<li>Two new graph classes (undirected and directed) which are intended
|
||||
to make the library more approachable for new developers</li>
|
||||
<li>A suite of graph measures including degree and closeness
|
||||
centrality, mean geodesic distance, eccentricity, and clustering
|
||||
coefficients.</li>
|
||||
<li>An algorithm for visiting all cycles in a directed graph (Tiernan's
|
||||
from 1970ish). It works for undirected graphs too, but reports cycles
|
||||
twice (one for each direction).</li>
|
||||
<li>An algorithm for visiting all the cliques a graph (Bron&Kerbosch).
|
||||
Works for both directed and undirected.</li>
|
||||
<li>Derived graph measures radius and diameter (from eccentricity) and
|
||||
girth and circumference (from Tiernan), and clique number (from
|
||||
Bron&Kerbosch).</li>
|
||||
<li>An exterior_property class that helps hides some of the weirdness
|
||||
with exterior properties.</li>
|
||||
<li>runtime and compile-time tests for the new algorithms.</li>
|
||||
<li>a substantial amount of documentation</li>
|
||||
<li>Graph cores, implemented by David Gleich (@Stanford University)</li>
|
||||
<li>Deterministic graph generators - capable of creating or inducing
|
||||
specific types of graphs over a vertex set (e.g., star graph, wheel
|
||||
graph, prism graph, etc). There are several other specific types that
|
||||
could be added to this, but I haven't had the time just yet.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="libraries-under-development">
|
||||
<h1>Libraries under development</h1>
|
||||
<div class="section" id="dataflow">
|
||||
<h2>Dataflow</h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body">Stjepan Rajko</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body">The Dataflow library provides generic support for data
|
||||
producers, consumers, and connections between the two. It also
|
||||
provides layers for several specific dataflow mechanisms, namely
|
||||
Boost.Signals, VTK data/display pipelines, and plain
|
||||
pointers. The Dataflow library came out of the Signal Network
|
||||
GSoC project, mentored by Doug Gregor.</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Status:</th><td class="field-body">I am polishing the Dataflow library for submission, and am expecting
|
||||
to add it to the review queue in the next couple of months.
|
||||
I am currently ironing out some faults in the design of the library,
|
||||
filling in missing features, and testing it on / adapting it to
|
||||
different dataflow mechanisms (currently VTK and soon
|
||||
Boost.Iostreams). As soon as I'm pretty sure that things are going
|
||||
the right way, I'll submit this to the review queue while I do the
|
||||
finishing touches.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
</div>
|
||||
<div class="section" id="constrained-value">
|
||||
<h2>Constrained Value</h2>
|
||||
<blockquote>
|
||||
<table class="docutils field-list" frame="void" rules="none">
|
||||
<col class="field-name" />
|
||||
<col class="field-body" />
|
||||
<tbody valign="top">
|
||||
<tr class="field"><th class="field-name">Author:</th><td class="field-body"><p class="first">Robert Kawulak</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Download:</th><td class="field-body"><p class="first"><a class="reference external" href="http://rk.go.pl/f/constrained_value.zip">http://rk.go.pl/f/constrained_value.zip</a></p>
|
||||
<p><a class="reference external" href="http://rk.go.pl/r/constrained_value">http://rk.go.pl/r/constrained_value</a> (Documentation)</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Description:</th><td class="field-body"><p class="first">The Constrained Value library contains class templates
|
||||
useful for creating constrained objects. The simplest example
|
||||
of a constrained object is hour. The only valid values for an hour
|
||||
within a day are integers from the range [0, 23]. With this library,
|
||||
you can create a variable which behaves exactly like int, but does
|
||||
not allow for assignment of values which do not belong to the
|
||||
allowed range. The library doesn't focus only on constrained
|
||||
objects that hold a value belonging to a specified range (i.e.,
|
||||
bounded objects). Virtually any constraint can be imposed using
|
||||
appropriate predicate. You can specify what happens in case of
|
||||
assignment of an invalid value, e.g. an exception may be thrown or
|
||||
the value may be adjusted to meet the constraint criterions.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr class="field"><th class="field-name">Status:</th><td class="field-body"><p class="first last">I'm planning to finish it in 1-2 months.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
<p>Please let us know of any libraries you are currently
|
||||
developing that you intend to submit for review.</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
Loading…
Reference in New Issue
Block a user