Nabble - Boost

Re: Re view Queue Needs Attention

2009-11-24T21:07:36Z

>> What's the difference between a non-stable branch as you're suggesting and
>> the existing sandbox? The only difference I could see is to establish some
>> kind of pre-review process. But that would just move the problem to a
>> different spot, no?

The "non-stable" branch would be for libraries that have requested reviews
or for "approved" libraries that have not yet stabilized.

The "sand-box" branch would be for all other libraries that either have not
requested reviews or don't plan to.

The "review-wizards" John or Ronald or any of the "boost-moderators"
could monitor the
"non-stable" branch.

This would clear the review queue.

The only important review would be to establish when a particular
library has achieved sufficient maturity
to be moved from the "non-stable" branch to the "stable" branch.

Once a library is in the "non-stable" branch, the library could be
reviewed by anyone anytime.
There would be no need for scheduled reviews, like we've had, although
they could
still be done, if the review manager wants to schedule it.

The reviews would be ongoing and done in a blog format, not limited to
a ten day block of time.

After a library has been in the "non-stable" branch for say six
months, the review manager could
posts its progress to the mailing list and pose questions to elicit
more feedback.

The "non-stable" branch would be included as part of the boost
installation, but only an
optional part, not required.

If a library is distributed as "non-stable", it
should get lots and lots of attention. Nothing focuses an authors
mind more than
if they know that their library is going to get some exposure.

The libraries in the review queue are not getting the exposure that
they need, and
are just sitting there for 6-18 months. Very few people are actually aware
of these libraries.

A better job needs to done to elicit feedback from domain experts. Having
only a 10 day review period is way to short. It needs to be like 6-12 months,
where the domain experts can contribute at their leisure.

This could best be done if a "non-stable" branch is created, which is
distributed
along with the "stable" branch.
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: Core libraries should separated from experimentallibraries

2009-11-24T21:06:47Z

Jeffrey Bosboom wrote:

> OvermindDL1 wrote:
>> On Tue, Nov 24, 2009 at 10:08 AM, Robert Ramey <ramey@...> wrote:
>>> Christian Schladetsch wrote:
>>>> +1 for making it harder to add a new library to boost.
>>>>
>>>> There are already too many libraries.
>>>>
>>> -1 for making it even harder to add a new library to boost.
>>>
>>> Boost and C++ doesn't have anywhere near enough libraries.
>>
>> -1 too.
>>
>> Other languages are more popular just *because* they have libraries
>> that do everything, we need such things in C++ too, with the speed
>> that C++ provides us. You can never have too many libraries, as long
>> as they are well documented and categorized.
>
> I believe Christian's response may have more to do with Boost's
> monolithic nature. It isn't currently possible to say "I need
> shared_ptr and Boost.Unordered and any necessary dependencies" -- the
> user must install all of Boost, which is daunting if not as difficult
> as it first seems. This goes against the C++ philosophy of "you only
> pay for what you use". This problem will only get worse as Boost
> accumulates more libraries.
>
> I also want more libraries (so here's my -1), and I've used Java
> largely on the strength of its standard library (especially Swing).
> In fact, I want them even if it makes Boost large and unwieldy. But I
> think making Boost modular would do a great deal to assuage the fears
> of those who would rather be more selective.
>
> --Jeffrey Bosboom
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost
>

I think what has to be done is that boost needs to be able to be seen as
the STL/MFC/ATL/etc by its potential users. If you look at the
complexity of the libraries shipped w/ visual studio, I think you might
see similar complexities as to what boost has, the difference is that
the user has to do absolutely nothing but install visual studio to gain
access to everything. Linux distros have similar painless installations
of C++ standard libraries too.

I'll give an example of how things shouldn't be. I consider myself a
pretty advanced windows user, I have a couple of scripts and a standard
setup for configuring boost the way I want on windows. However, when I
moved to linux (where i have 0 experience) I tried to set up the same
configurations for boost there, however, whenever I built the debug
version of the library and installed it, it overwrote the optimized
versions. So I gave up pretty quickly and moved on to other more
important things.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: Optional Attribute handling

2009-11-24T20:46:28Z

> >> After much experimentation I think I'm finally getting the hang of
> >> this. The key insight that I was lacking is that spirit doesn't
> >> generally collapse attributes in the way that I had hoped it would.
> >> Basically I was hoping for it to collapse as follows:
> >>
> >> a: A, b: optional<A> --> (a >> b): vector<A>
> >>
> >> This would be analogous to the current rule:
> >>
> >> a: A, b: vector<A> --> (a >> b): vector<A>
> >
> > Hmmm. Actually this should work. I just added a test case to the Qi
> sequence
> > tests:
> >
> > {
> > std::vector<char> v;
> > BOOST_TEST(test_attr("ab", char_ >> -char_, v));
> > BOOST_TEST(v.size() == 2);
> > BOOST_TEST(v[0] == 'a');
> > BOOST_TEST(v[1] == 'b');
> > }
> >
> > which passes just fine.
>
> Hmm, yes, you're quite correct. Perhaps the doco needs to be updated
> with these rules
>
> a: A, b: vector<A> --> (a >> b): vector<A>
> a: vector<A>, b: optional<A> --> (a >> b): vector<A>

Well, that's not entirely true. The rules you're referring to are used to
get the type of the computed attribute (that's the one which is assumed to
be returned by a parser if no data is supplied to this parser from the
user). For this we can't just get rid of the optional as it may change the
meaning of the parser (or its result).

The other case to be considered, though, and that's what I was referring to,
is which attribute types are compatible with a parser. This is slightly
different from the computed attribute type as more than one type might be
usable as the target for a specific parser. In our case we can provide a
plain type (non-optional) to a parser which normally returns an optional
just fine, because the plain type is compatible. Both we can use as the
target of an assignment where the plain type is on the rhs. We have not yet
come up with a formalized way of expressing attribute compatibility. Neither
in code nor on paper, sorry. We are planning to add a meta-function
is_attribute_compatible<> allowing to determine whether a given type can be
passed as the attribute to a given parser.

> On the other hand, this doesn't work:
>
> a: vector<A>, b: optional<vector<A> > --> (a >> b): vector<A>
>
> Here's a simplified version of my test case, but it does not compile:
>
>
> #define BOOST_TEST_MODULE spirit test
> #include <boost/test/unit_test.hpp>
>
> #include <boost/spirit/include/qi.hpp>
>
> namespace qi = boost::spirit::qi;
> namespace ascii = boost::spirit::ascii;
>
> BOOST_AUTO_TEST_CASE(TestParsing)
> {
> using ascii::digit;
> using qi::char_;
>
> const std::string input("123.456");
> std::string result;
> std::string::const_iterator begin = input.begin();
> BOOST_CHECK(qi::parse(begin, input.end(), +digit >> -(char_('.') >>
> +digit), result));
> BOOST_CHECK(begin == input.end());
> BOOST_CHECK_EQUAL(result, input);
> }
>
> Here, I would have expected the attributes to coalesce as follows:
>
> tuple< vector<char>, optional< tuple<char, vector<char> > > >
> tuple< vector<char>, optional< vector<char> > >
> tuple< vector<char>, vector<char> >
> vector<char>
>
> Is this a reasonable expectation?

Again, you can't just drop the optional from the computed attribute type.
But I will look into the code (later, probably tomorrow) whether it's
possible to make a vector<char>/string compatible with your sequence.

Regards Hartmut

-------------------
Meet me at BoostCon
http://boostcon.com

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Spirit-general mailing list
Spirit-general@...
https://lists.sourceforge.net/lists/listinfo/spirit-general

From forum: spirit-general

Re: Core libraries should separated from experimentallibraries

2009-11-24T20:23:00Z

OvermindDL1 wrote:

> On Tue, Nov 24, 2009 at 10:08 AM, Robert Ramey <ramey@...> wrote:
>> Christian Schladetsch wrote:
>>> +1 for making it harder to add a new library to boost.
>>>
>>> There are already too many libraries.
>>>
>> -1 for making it even harder to add a new library to boost.
>>
>> Boost and C++ doesn't have anywhere near enough libraries.
>
> -1 too.
>
> Other languages are more popular just *because* they have libraries
> that do everything, we need such things in C++ too, with the speed
> that C++ provides us. You can never have too many libraries, as long
> as they are well documented and categorized.

I believe Christian's response may have more to do with Boost's
monolithic nature. It isn't currently possible to say "I need
shared_ptr and Boost.Unordered and any necessary dependencies" -- the
user must install all of Boost, which is daunting if not as difficult as
it first seems. This goes against the C++ philosophy of "you only pay
for what you use". This problem will only get worse as Boost
accumulates more libraries.

I also want more libraries (so here's my -1), and I've used Java largely
on the strength of its standard library (especially Swing). In fact, I
want them even if it makes Boost large and unwieldy. But I think making
Boost modular would do a great deal to assuage the fears of those who
would rather be more selective.

--Jeffrey Bosboom
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: Proposal for library addition: faster signals/slots, reactor, atomics

2009-11-24T20:12:33Z

Helge Bahmann wrote:
> Hello everyone
>
> I have written a small library providing:
>
> - a (thread-safe) signal/slot implementation
> - poll/timer/reactor implementation
> - atomic operations modelled after the proposed C++0x standard (x86 32/64 bit,
> ppc, alpha, more if someone donates hardware; fallback implementation using
> locks)

I'm not really interested in the signals/slots implementation or the
reactor, but I'm very interested in an implementation of the C++0x
standard atomics. I encourage you to split the atomics from the other
parts of the library, since they will be useful in many more contexts
(including other Boost libraries).

--Jeffrey Bosboom
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Spirit.Qi: issues with incompatible type

2009-11-24T20:12:06Z

I have problem compiling the following grammar. I believe the issue is something to do with the highlighted line (string("name:")[_val += _1].

rule<Iterator, string(), ascii::space_type> NameTag;

rule<Iterator, string(), ascii::space_type> Name;

symbols<> Tag;

NameTag = Tag [_val += _1]

>>string("name:") [_val += _1]

>> Name [_val += _1];

Name %= +alnum;

What did I do wrong here ?

Thanks

Mr H

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Spirit-general mailing list
Spirit-general@...
https://lists.sourceforge.net/lists/listinfo/spirit-general

From forum: spirit-general

Re: Review Queue Needs Attention

2009-11-24T19:53:18Z

Stefan Strasser-2 wrote:

Zitat von Tom Brinkman <reportbase@gmail.com>:

> The number of review requests is
> far outstripping the number of volunteer review managers.

is the lack of review managers the bottleneck of the review process right now?

I`m relatively new to boost, but judging from the "notes for review
managers" on the website that doesn`t sound like a lot of work.
I'm planning to submit a library for review myself, and the prospect
that that'd take 2 years isn't very encouraging, so I'd probably
volunteer just for this reason alone.

This is exactly what I did.

maybe you could regularly post a call for review managers to the
mailing list, with a list and a short description of libraries in need
of a review manager?

The review wizard make a report regularly on the Past Review Results and Milestones page (http://www.boost.org/community/review_schedule.html) including the information you are requesting

Review Wizard Status Report Ronald Garcia June 4, 2009
Report (http://www.boost.org/development/report-jun-2009.html)

Best,
Vicente

From forum: Boost - Dev

Re: Review Queue Needs Attention

2009-11-24T19:45:18Z

Tom Brinkman-2 wrote:

>> judging by the review schedule (almost no review managers), that would mean
>> boost isn't very interested in new libraries in general.

It would seem so.

>> I would recommend that authors try find a review manager before they request a review.

Review managers are generally recruited from people that already have a library
that has been approved in boost, that means you luke (hint).

The wizards could open it up to anyone. Its been considered, but
rejected in the past.

I would like to focus attention on something different.

That would be creating a "non-stable"
branch of boost, where the proposed libraries would live for a while, get some
exposure.

There had already a lot of review managers that do not have a library accepted, for example

Thread-Safe Signals Frank Hess Stjepan Rajko
Finite State Machines Andrey Semashev Martin Vuille
Singleton (fast-track) Tobias Schwinger John Torjo
Switch Steven Watanabe Stejpan Rajko
Physical Quantities System Andy Little Fred Bertsch
binary_int Scott Schurr and Matt Calabrese Pavel Vozenilek
Xpressive Eric Niebler Thomas Witt
Typeof Arkadiy Vertleyb and Peder Holt Andy Little
Singleton Jason Hise Pavel Vozenilek
State Chart Andreas Huber Pavel Vozenilek
Promotion Traits (fast-track) Alexander Nasonov Tobias Schwinger
Output Formatters Reece Dunn John Torjo
FC++ Brian McNamara & Yannis Smaragdakis Mat Marcus
Fixed-Point Decimal Bill Seymour Jens Maurer
Math Constants Paul A. Bristow Jaap Suter
...

and there are other on the review queue

AutoBuffer Thorsten Ottosen Robert Stewart
Task Oliver Kowalke Vicente Botet

without forgotten the review Wizard John R. Phillips and Tom Brinkman

Accumulators Eric Niebler John R. Phillips
Function Types (Re-review) Tobias Schwinger Tom Brinkman
Generic Image Library Lubomir Bourdev Tom Brinkman
Wave Hartmut Kaiser Tom Brinkman

As you can see review manager is not restricted to library authors. I call any invested booster to request the possibility to be the review manager of a library if he knows the domain.

Since most libraries are header file only, it should not be a problem.
While not all
will compile on all platforms, and certainly not have perfect
documentation, it would
be a place for future boost authors to elicit feedback.

The experimental libraries would not affect the core boost libraries
in any way.

I'm absolutely convinced that it would encourage lots more participation.

There is so much more to do, we haven't even scratched the surface of what
is possible. The core boost authors have put in place a wonderful place
to come and share ideas, but we are letting it flounder.

I don't see clearly which will be the criteria for including a library in this non-stable group. Any suggestions?
Which test platforms will be available to test the non-stable libraries, the same as the trunck?
Will these libraries be delivered?
Doesn't the Sandbox pays already the role of non-stable libraries?

Best,
Vicente

From forum: Boost - Dev

Re: Review Request: boost.lockfree

2009-11-24T19:33:15Z

> - that free_list thing...looks very much like an allocator.
> I understand that you want to make sure that push/pop doesn't call the default allocator (-> mutex lock), but couldn't you make lock-free containers accept stateful allocators and provide a default allocator that keeps free-d objects in a free_list?
> am I missing a reason why you need a seperate allocation interface? I haven't found the concept the free_list_t template parameter in the documentation, can it do anythiong beyond what the interface of a std::allocator provides?
>

typically with lockfree it is hard to truly free anything because some
thread may still be lingering on the node you are freeing. So you need
a free list that maybe recycles but never actually frees.
IIRC that is the case with this library, unless it has changed since I
first saw it.

Tony
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: Review Queue Needs Attention

2009-11-24T19:26:33Z

> I would like to focus attention on something different.
>
> That would be creating a "non-stable"
> branch of boost, where the proposed libraries would live for a while,
> get some
> exposure.
>
> Since most libraries are header file only, it should not be a problem.
> While not all
> will compile on all platforms, and certainly not have perfect
> documentation, it would
> be a place for future boost authors to elicit feedback.
>
> The experimental libraries would not affect the core boost libraries
> in any way.
>
> I'm absolutely convinced that it would encourage lots more
> participation.

What's the difference between a non-stable branch as you're suggesting and
the existing sandbox? The only difference I could see is to establish some
kind of pre-review process. But that would just move the problem to a
different spot, no?

Regards Hartmut

-------------------
Meet me at BoostCon
http://boostcon.com

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: [thread] Bug sprint: #2100 thread fails to compile with -fno-exceptions

2009-11-24T19:14:21Z

Bugzilla from anthony.ajw@gmail.com wrote:

Vicente Botet Escriba <vicente.botet@wanadoo.fr> writes:

> Ticket description: "The thread component fails to compile with GCC when
> -fno-exceptions is specified. The attached patch allows the libraries /
> tests shipped with boost 1.35.0 to compile. There didn't seem to be a better
> option to make g++ happy than to just #ifndef out the catch(...) block, as
> it would otherwise complain about the throw in the block." from
> https://svn.boost.org/trac/boost/ticket/2100
>
> Hi, I think that Boost.Thread has not been designed to work without
> exception. What would be the behavior of the application if we remove just
> any throw statement? In order to achieve the reporter goal, we should need
> to add functions returning a return code. IMO this is out of the scope
> currently. Thus I propose to close the ticket.

I've committed a change to trunk that uses boost::throw_exception in
most cases. The only cases I haven't touched are where
thread_interrupted is thrown at a cancellation point.

As you say, Boost.Thread has not been designed to work without
exceptions. In most cases this is not a problem, but interruption relies
on exceptions to work properly. I'm therefore inclined to think that
interruption should not be available with exceptions disabled, in which
case this code can be masked with a #ifdef

What do you think?

Hi,

the use of boost::throw_exception is welcome but more for the ability this function provides to store a pointer to an exception than the ability to disable exception. If in addition you use some ifdefs to mask features that are not easy to provide without exceptions the reporter of the ticket could use Boost.Thread on an environment that has or requires no exceptions.

I don't understand however how an application can work without taking care of errors. Just my point of view.

Thanks,
Vicente

From forum: Boost - Dev

Re: [Exception] SFINAE use breaks Borland in Trunk

2009-11-24T17:29:35Z

On Tue, Nov 24, 2009 at 4:13 AM, John Maddock <john@...> wrote:

>>> The issue appears to be use of SFINAE like techniques without a
>>> BOOST_NO_SFINAE fallback.
>>>
>>> The problem here is that since Boost.Exception gets pulled in by almost
>>> everything, we need it to be lightweight and well supported, otherwise
>>> the
>>> rest of us are stuck even if we want to continue to support the older
>>> compilers :-(
>>
>> The only part of Boost.Exception that is pulled in by almost all Boost
>> source files that throw exceptions is boost/throw_exception.hpp. It is
>> very lightweight and works on all compilers (including Borland), at
>> least to the extend of being able to call boost::throw_exception to
>> throw.
>>
>> With the rest of Boost.Exception, Borland has many issues. Of course,
>> I am not against supporting that compiler, I would certainly accept
>> patches to that effect.
>
> Maybe this is a Boost.Test issue then, because that's where the failure
> occurs, which means we can't actually test anything with this compiler :-(

Where does the failure occur? The tests that must (and do) pass on all
platforms and compilers are the top four lines in the Boost.Exception
test matrix: http://www.boost.org/development/tests/trunk/developer/exception.html.

Emil Dotchevski
Reverge Studios, Inc.
http://www.revergestudios.com/reblog/index.php?n=ReCode
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

First results using Comeau C/C++ compiler

2009-11-24T16:08:43Z

Hi,

After quite some time of trying to build Boost, especially Boost.Test,
using Comeau C/C++ frontend with GCC 4.x on Linux, I've started to get
some promising results.

During this investigation I was juggling number of fixes
and patches [1] and eventually I found quite surprising solution.
Yesterday, while reading signal.h and other headers to find out
how to get signals features compiling for Boost.Test library,
I came across an interesting macro which seems to be a passkey
to the world of GNU C Library for Comeau toolset :-)

It is _GNU_SOURCE macro [2]:

"If you define this macro, everything is included: ISO C89, ISO C99,
POSIX.1, POSIX.2, BSD, SVID, X/Open, LFS, and GNU extensions."

Defining this macro seems to solve all issues I reported [1] so far.
BTW, I've sent request to Comeau team for their opinion about usage of
this macro with Comeau C/C++ frontend. Hopefully, it will be assumed
safe to use, then we've got solution for all/most of the problems.

Second due to the fact Comeau does not support linking as shared,
I had to explicitly request to link Boost.Test binaries statically.

I attach patch for Boost.Test Jamfile.v2 files adding the macro and
configuring static link for como toolset.
Let it be an example showing what kind of changes/options are needed by
como toolset to build Boost.Test binaries.
I haven't tried, but I suppose it's safe to assume that the same
changes are needed to build other libraries like Asio, Program Options,
and others. I'm going to find it out.

To summary, there are two required changes in build configuration to
enable como toolset, so far.
So, what is the best approach to incorporate those two settings to other
libraries (only those when it's needed):
* Should I hack all Jamfiles where those changes are needed?
* Or, it would make sense to set these options for como toolset,
by default?
* Where <link>static should go? To Jamfiles or nowhere and static
linking should be explicitly enabled as bjam argument?
I also tested: como --v2 link=satic

Gennadiy, I'm sorry for making quite a mess in Trac by reporting number
of tickets and submitting number of patches which eventually turned out
to be unnecessary. It took me number of iterations to sort it out
and I was subsequently recording my discoveries.

[1]
- int64_t/uint64_t
https://svn.boost.org/trac/boost/ticket/3548
- snprintf, vsnprintf
https://svn.boost.org/trac/boost/ticket/3558
- POSIX features (e.g. signals.h)
https://svn.boost.org/trac/boost/ticket/3662

[2] _GNU_SOURCE
http://www.gnu.org/software/libc/manual/html_node/Feature-Test-Macros.html

Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org

Index: libs/test/build/Jamfile.v2
===================================================================
--- libs/test/build/Jamfile.v2 (revision 57917)
+++ libs/test/build/Jamfile.v2 (working copy)
@@ -13,6 +13,8 @@
<link>shared,<toolset>msvc:<cxxflags>-wd4275
<toolset>msvc:<cxxflags>-wd4671
<toolset>msvc:<cxxflags>-wd4673
+ <toolset>como:<link>static
+ <toolset>como-linux:<define>_GNU_SOURCE=1
<warnings>all
: usage-requirements
<define>BOOST_TEST_NO_AUTO_LINK=1
@@ -107,4 +109,4 @@
boost-install boost_prg_exec_monitor
boost_test_exec_monitor
boost_unit_test_framework ;
-
\ No newline at end of file
+
Index: libs/test/test/Jamfile.v2
===================================================================
--- libs/test/test/Jamfile.v2 (revision 57917)
+++ libs/test/test/Jamfile.v2 (working copy)
@@ -23,6 +23,8 @@
<toolset>borland:<cxxflags>-w-8084
<toolset>msvc-6.5:<link>static
<toolset>msvc-8.0:<define>_SCL_SECURE_NO_DEPRECATE
+ <toolset>como:<link>static
+ <toolset>como-linux:<define>_GNU_SOURCE=1
<warnings>all
: $(test-name)
] ;
@@ -44,6 +46,8 @@
<toolset>borland:<cxxflags>-w-8080
<toolset>msvc-6.5:<link>static
<toolset>msvc-8.0:<define>_SCL_SECURE_NO_DEPRECATE
+ <toolset>como:<link>static
+ <toolset>como-linux:<define>_GNU_SOURCE=1
<define>BOOST_TEST_NO_AUTO_LINK=1 # requirements
<threading>multi
: $(test-name)
Index: libs/test/tools/console_test_runner/Jamfile.v2
===================================================================
--- libs/test/tools/console_test_runner/Jamfile.v2 (revision 57917)
+++ libs/test/tools/console_test_runner/Jamfile.v2 (working copy)
@@ -6,7 +6,12 @@
# See http://www.boost.org/libs/test for the library home page.

# Project
-project libs/test/tools/console_test_runner ;
+project libs/test/tools/console_test_runner
+ :
+ : requirements
+ <toolset>como:<link>static
+ <toolset>como-linux:<define>_GNU_SOURCE=1
+ ;

alias unit_test_framework
: # sources
Index: libs/test/example/Jamfile.v2
===================================================================
--- libs/test/example/Jamfile.v2 (revision 57917)
+++ libs/test/example/Jamfile.v2 (working copy)
@@ -12,7 +12,10 @@
# Project
project libs/test/example
:
- : requirements <toolset>msvc-6.5:<link>static
+ : requirements
+ <toolset>msvc-6.5:<link>static
+ <toolset>como:<link>static
+ <toolset>como-linux:<define>_GNU_SOURCE=1
;

# Define aliases for the needed libs to get shorter names

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

--
Mateusz Loskot
http://mateusz.loskot.net

From forum: Boost - Dev

Re: [serialization] how to serialize map ofnon-default-constructible?

2009-11-24T15:28:28Z

<ivo.t@...> wrote in message
news:ECB13B9D09204914A385D25B334DF831@Ivo2...
> Hi to everybody,
>
> I'm new to the list, work for some time with Boost and C++ and have a
>
> fair knowledge but am not an expert yet. I try to serialize a map whose
> type

This is really a question for the boost users group, but...

> ist not default-constructible, and I'm seriously stuck there. I thought
> the
> load_construct_data and save_construct_data overrides would help me there,
> but that seems not to be the case. I tried to create a private default
> constructor hoping that the map (respectively pair) constructor could
> access

This is because boost::serialization does not put any special handling in
for std::pair when serialized via std::map.

It is the default construction of the pair that trips you up.

> it, due to the boost::serialization::access friend declaration, but that
> didn't work as well. I really do _not_ want to make a public default
> constructor. What could I do as a workaround??

You could specialize the construct_data functions for the pair (i.e. the
map's value_type), e.g.:

////////
// Example, non-default constructable class
class X
{
public:
X(int i) : i_(i) {}

private:
int i_;
friend class boost::serialization::access;
template <typename A>
void serialize(A &ar, const unsigned)
{
ar & i_;
}
};

template <typename A>
inline void load_construct_data(A &ar, X * x, const unsigned)
{
::new(x)X(1); // e.g.
}
////////

typedef std::map<int, X> Map;
typedef Map::value_type PairType;

template <typename A>
inline void serialize(A &ar, PairType &p, const unsigned)
{
// Do nothing, handled by xxxx_construct_data
}

template <typename A>
inline void save_construct_data(A &ar, const PairType *p, const unsigned v)
{
using namespace boost::serialization;
ar << make_nvp("first", p->first);
save_construct_data(ar, &p->first, v);
ar << make_nvp("second", p->second);
save_construct_data(ar, &p->second, v);
}

template <typename A>
inline void load_construct_data(A &ar, PairType *p, const unsigned v)
{
using namespace boost::serialization;
typedef BOOST_DEDUCED_TYPENAME
boost::remove_const<PairType::first_type>::type typef;
load_construct_data(ar, &const_cast<typef &>(p->first), v);
ar >> make_nvp("first", const_cast<typef &>(p->first));

load_construct_data(ar, &p->second, v);
ar >> make_nvp("second", p->second);
}

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

[Ubuntu 8.04] Linking Problem in Eclipse with Boost 1.41 Libraries

2009-11-24T14:45:48Z

Hello all,

My question is concerning the Boost installation process. I am
currently working on a machine that has Ubuntu 8.04 LTS. I have
downloaded the latest copy of Boost (1.41.0) and am trying to
successfully install it. I have followed the procedures for building
the libraries such as Filesystem / Regex / Thread / etc. using both
the bootstrap, "easy", method and the "build custom binaries" method.

I'm using Eclipse as my C++ development environment and I can create
programs that use the Boost headers (the ones that do not require
compilation - ie. Lambda) just fine. When I try to implement the
sample program that incorporates [regex], I am able to compile and
link just fine. I've set the include directory to (
/usr/local/boost_1_41_0/prefix/include - prefix was just the name I
gave the folder), the library search path to (
/usr/local/boost_1_41_0/prefix/lib ) and the library I wanted to link
to, [regex], using (boost_regex - I have also tried
boost_regex-gcc##-mt ).

As I said though, when I try to run the program, I get the result:

./boost_regex_test: error while loading shared libraries:
libboost_regex.so.1.41.0: cannot open shared object file: No such file
or directory

I have not specified that I was using shared libraries, so I do not
understand why it is trying to look for them. If anyone could please
clarify why this is happening, I'd be more than greatful.

Just as an aside, I also tried downloading and installing Boost from
the Synaptic Package Manager that comes with Ubuntu 8.04. I'm able to
use all of the libraries when I do this, but I'd rather not because
the version of Boost is 1.34.1 (quite archaic) and has cause problems
because member variables have evolved and some no longer exist.

Thanks again for any and all help.
_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

Re: [filesystem]: infinite-recursion with symlink

2009-11-24T14:44:48Z

On Tue, Nov 24, 2009 at 4:03 PM, Beman Dawes <bdawes@...> wrote:

> On Tue, Nov 24, 2009 at 10:16 AM, Zachary Turner <divisortheory@...
> >wrote:
>
> >
> > a) timestamp operations
> >
>
> Which specific timestamp operations do you need? Last write time is already
> supported.
>

All timestamps which are gettable / settable via system calls. In windows
this means create/access/modify, and posix this means create/modify/change.
One of the posix ones I believe is actually not settable.

>
>
> > b) cross-platform create/open of files
> >
>
> Nothing planned, beyond the current <fstream> support.
>
Unfortunate, as there is really quite a bit in common between the two
operating systems' create/open methods that could be exploited. For example
(here, <-> means either equivalent or more or less equivalent):

O_DIRECT <-> FILE_FLAG_NO_BUFFERING|FILE_FLAG_WRITE_THROUGH
O_NONBLOCK <-> FILE_FLAG_OVERLAPPED
O_CREAT | O_EXCL <-> CREATE_NEW
O_CREAT | O_TRUNC <-> CREATE_ALWAYS

You can abstract these into an enumeration such as create_direct,
create_async, etc but also define all the platform specific ones as well and
allow them to be combined with the generic ones.

Other areas of boost require handles to operate on. For example,
boost::asio supports asynchronous operations but requires a handle that's
been opened with the appropriate flags (FILE_FLAG_OVERLAPPED, for example).
It actually doesn't support async i/o for posix filesystem handles, but I
have my own extensions to boost::asio that do allow this and map to the
posix aio_* family of apis, and requires a handle that's been opened with
O_NONBLOCK.

boost::iostreams already supports a cross platform file descriptor / handle,
but there is currently no cross-platform way to actually create such a
handle. So I have the feeling that almost anyone using
boost::iostreams::file_descriptor is using ifdefs all over their code to
create the handles. Correct me if this is wrong.

>
>
> > c) windows junctions and symlinks
> >
>
> Supported in V3.
>

What types of operations are supported for junctions and symlinks? Can I
query the target to see what it points to, and is there an api(s) that
allows delete to selectively delete the target or the original item?

Also I forgot to mention hard links. If hard links are supported, can i
query the link count or get the inode number? (Contrary to popular belief,
all versions since windows 2000 support hard links and the ability to get an
inode # for a file).

>
>
> > d) unix block/char devices, sockets, and pipes
> >
>
> Nothing planned in Boost.Filesystem. Several other Boost libraries already
> have at least some support for these.
>

If boost.filesystem supported them, I could create them using a consistent
interface to how I create other types of filesystem objects, and also be
able to use any timestamp functionality provided by Boost.Filesystem to
query them.

>
>
> >
> > create/open is the biggest gaping hole in the current FS library in my
> > opinion. you often just need a handle and want to customized the way in
> > which it's opened. with my code you can do soemthing like:
> >
> > filesystem::handle handle; /* opaque structure, only understood by
> the
> > filesystem api */
> > filesystem::object_info info; /* boost variant, internal type depends
> on
> > type of filesystem object */
> >
> > filesystem::create_file(
> > path,
> > link_open_target, /* follow symlinks */
> > only_dir, /* fail unless this is a directory handle
> > */
> > flags::async | flags::direct | flags::bypass_security, /*
> > open for async direct i/o and disable any kernel security checking */
> > &handle, /* have the function return the handle
> (this
> > can be null if not interested) */
> > &info; /* have the function return object info
> > (this can be null if not interested) */
> > );
> >
> > handle then is an opaque object that can be used by other filesystem apis
> > like timestamp operations etc, and info is a boost::variant whose type
> > depends on whether it's a directory, junctino, symlink, pipe, etc.
> >
>
> Nothing like that planned at the moment.
>
> I've solved all of the above problems in a cross-platform way in my own
> > in-house api but it might be difficult to integrate any of what i've done
> > into an interface consistent with the current filesystem library. if you
> > want any of this code though let me know.
> >
>
> What I'd be most interested in is motivation and use cases. I need to
> better
> understand the need before I start thinking about code.

Well, I work on high performance backup software for linux/windows. For
backup I need raw access to the disk, this means I need fine control over
the handle that I'm performing I/O on. In particular, it needs to be
asynchronous and support unbuffered i/o but there are various other cases
where I use strange combinations of flags (for example
FILE_FLAG_SEQUENTIAL_SCAN or FILE_FLAG_DELETE_ON_CLOSE on windows). Some
files however should not be backed up (depends on some custom rules
specified by the user) and for these I need to be able to recursively delete
them. But maybe sometimes I want to follow links and sometimes I don't,
again depends on some user parameters.

If performance were not such a high consideration this is not a problem.
But since it is, I need to do everything possible to minimize the number of
API calls and opens/closes on individual files. Consider for example a
system with millions of small files (say 0 bytes just for the sake of
argument). In this case just opening the file is 100% of the work that
needs to be done on this file, so I should try to open it as few times as
possible. However, first I have to know that it's even a normal file and
not some directory that I need to recurse into. So I check if it's a file,
it is so then I can open it and start reading from it. But issuing two
calls via a path is going to be much slower than first getting a handle to
the object and then querying the handle for the required information. Then,
without even opening it again, I can use the same handle to actually read
data from the file, saving costly operations.

There are many examples of optimizations such as this, but ultimately it
boils down to the fact that operations on handles are much faster than
operations on paths, and handles can also be used to actually perform i/o
on.

As for restore, I need to be able to set every possible aspect of a file
that exists, including all timestamps, permissions, and I need to be able to
restore any type of file whether it be a socket, pipe, or windows junction.
Again, I need fine grained control over the handle. For example, on
windows I need FILE_FLAG_BACKUP_SEMANTICS to disable ACL security checking.

90% of this can be abstracted into things that are common between each
platform. For the parts that can't, I really like the model that Boost.Asio
has employed, where it provides a windows and posix namespace and provides
all the extra details there.

Zach
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: BGL: counting connected components subgraph

2009-11-24T14:41:47Z

Hi!

> How to walk over those separate trees?

If you need the trees too I suggest using prim_minimum_spanning_tree
becuse the predecessor map in Kruskal's algorithm is used for the
disjoint-set data structure to indicate which set a particular vertex
is in so it cannot be used walking the tree. I think
prim_minimum_spanning_tree is a better choice here because it supports
dijkstra visitors so you can mark tree edges on-the-fly and then use a
filtered_graph to hide every non-marked edges to walk the trees. You
can use the predecessor map exactly like in the first method to
identify root vertices.

Gabe
_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

Re: issues with setting properties on reverse graph

2009-11-24T14:37:27Z

that fixed the issue
I actually just manually edited reverse_graph.pp and properties.hpp with your changes and it compiles and runs fine now.

Thanks Jeremiah

Jeremiah Willcock wrote:

On Tue, 24 Nov 2009, Mangal wrote:

>
>
> so this is what I see is happening
>
> if I use get_property(graph, propertyname) = propertyvalue
> to set the property on the graph then setting the property on reverse graphs
> does not work (even with the new typedef in the sample code i posted)
>
> however using set_property(graph, propertyname, propertyvalue) works when
> used with the new typedef.
> (even in my application)
>
> Thanks Jeremiah

Please try r57910; that should fix the get_property() issue.

-- Jeremiah Willcock
_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

Re: [thread] Bug sprint: #2100 thread fails to compile with -fno-exceptions

2009-11-24T14:32:39Z

Vicente Botet Escriba <vicente.botet@...> writes:

> Ticket description: "The thread component fails to compile with GCC when
> -fno-exceptions is specified. The attached patch allows the libraries /
> tests shipped with boost 1.35.0 to compile. There didn't seem to be a better
> option to make g++ happy than to just #ifndef out the catch(...) block, as
> it would otherwise complain about the throw in the block." from
> https://svn.boost.org/trac/boost/ticket/2100
>
> Hi, I think that Boost.Thread has not been designed to work without
> exception. What would be the behavior of the application if we remove just
> any throw statement? In order to achieve the reporter goal, we should need
> to add functions returning a return code. IMO this is out of the scope
> currently. Thus I propose to close the ticket.

I've committed a change to trunk that uses boost::throw_exception in
most cases. The only cases I haven't touched are where
thread_interrupted is thrown at a cancellation point.

As you say, Boost.Thread has not been designed to work without
exceptions. In most cases this is not a problem, but interruption relies
on exceptions to work properly. I'm therefore inclined to think that
interruption should not be available with exceptions disabled, in which
case this code can be masked with a #ifdef

What do you think?

Anthony
--
Author of C++ Concurrency in Action | http://www.stdthread.co.uk/book/
just::thread C++0x thread library | http://www.stdthread.co.uk
Just Software Solutions Ltd | http://www.justsoftwaresolutions.co.uk
15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: Review Queue Needs Attention

2009-11-24T14:31:45Z

>> judging by the review schedule (almost no review managers), that would mean
>> boost isn't very interested in new libraries in general.

It would seem so.

>> I would recommend that authors try find a review manager before they request a review.

Review managers are generally recruited from people that already have a library
that has been approved in boost, that means you luke (hint).

The wizards could open it up to anyone. Its been considered, but
rejected in the past.

I would like to focus attention on something different.

That would be creating a "non-stable"
branch of boost, where the proposed libraries would live for a while, get some
exposure.

Since most libraries are header file only, it should not be a problem.
While not all
will compile on all platforms, and certainly not have perfect
documentation, it would
be a place for future boost authors to elicit feedback.

The experimental libraries would not affect the core boost libraries
in any way.

I'm absolutely convinced that it would encourage lots more participation.

There is so much more to do, we haven't even scratched the surface of what
is possible. The core boost authors have put in place a wonderful place
to come and share ideas, but we are letting it flounder.

Ugh.
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: handling unicode strings / encodings?

2009-11-24T14:18:53Z

The xml_warchive of the serialization library uses this codecvt facet.

It's very easy to use for the purpose you describe.

Robert Ramey

Maróy Ákos wrote:

> Hi,
>
> I wonder what the state of handling unicode strings is in C++ / with
> boost? I've found some references to the codecvt<> feature, and also
> I've found utf8_codecvt_facet among the boost sources, but I can't
> really make it work.
>
> what I would need is to handle strings based on the whole unicode
> representation, and to encode them to UTF-8 and back.
>
> is there anything related in boost?
>
>
> Akos

_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

How to pass a parameter to a rule so that the client can pick the token to search for

2009-11-24T14:09:38Z

I am parsing a text based log file on a line by line basis and I want users to
be able to pass a string parameter that I will use to match lines in the log
file containing the passed in string. I will return the
hex bytes on that matching line that appear after the passed in string.
How do I simply pass this kind of parameter to a grammer object.
Given the following code: (Thanks to help from others on this list)

Is there a simple and clear way to do this?

template<class iterator>
struct junk_parser : qi::grammar<iterator>
{
// Gets rid of stuff before the token I am looking for
junk_parser() : junk_parser::base_type(start)
{
s = "STRING_TO_SEARCH_FOR";
delim = string(s)>> *qi::uint_;
start = *(qi::char_ - delim) >> delim;
}
qi::rule<iterator> start;
qi::rule<iterator> delim;
std::string s;
};

template<class iterator>
struct line_parser : qi::grammar<iterator,
qi::blank_type,
std::vector<unsigned char>()>
{
line_parser() : line_parser::base_type(line)
{
line = junk >> +hex2;
}
qi::rule<iterator,qi::blank_type,std::vector<unsigned char>()> line;
qi::uint_parser<unsigned char,16,2,2> hex2;
junk_parser<iterator> junk;
};

int CConsoleLogParser::getNextToken(std::vector<unsigned char>& v)
{
std::string line;

//assume the user has already set msgType to the desired NAMEX value
std::string msgType;

// How do I pass a string param to gram?
line_parser<std::string::iterator> gram;

std::vector<unsigned char> hexvalues;

while (! logFile.eof() )
{
getline (logFile,line); // Read the console log line by line
std::string::iterator first(line.begin());

if(qi::phrase_parse(first, line.end(),
gram, qi::blank, hexvalues ))
{
// handle the message here
std::cout << "Passed" << std::endl;
v.assign(hexvalues.begin(),hexvalues.end());
return (int)v.size();
}
else
{
// error parsing the line
std::cout << "Failed" << std::endl;
}
}
logFile.close();

return -1;
}

This is the kind of log file I am trying to parse
I want to store the hex digits after the NAMEX field in a vector
02:40:02 CCD dd <-: NAME1 00 1a 4c 04 13 00 00 02 00 00
02:40:02 ER MMD <-: NAME2 15 00 7e 00 98 28 40 90 0f 80
02:40:02 AF M44 <-: NAME3 4a 88 00 00 a0 00 05 22 aa d5
02:40:02 AF M32 ->: NAME4 20 88 1b 81 1f 44
02:40:02 CC M32 <-: NAME5 05 08 12 01 f0 02 15 38 57 05 f4 00 1f
TEST: UE_ ue_id:32 i:244221230000002
02:40:02 MM M32 ->: NAME6 05 12 01 11 f8

Thanks
Al

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Spirit-general mailing list
Spirit-general@...
https://lists.sourceforge.net/lists/listinfo/spirit-general

From forum: spirit-general

Is is possible to compile with cyclic dependencies?

2009-11-24T14:05:49Z

Hi Everyone,

while developing I realized that Boost.Build seems to have problems
with cyclic dependencies.

I have some applications that link to libraries, which themselves link
to other libraries. I want each application to automatically link to
all (indirectly) needed libraries, however, I do not want to write
down every indirectly used library into the creation-rule.
So, for each library, I am only writing down the directly needed/used
libraries into the "usage-requirements" of the lib-rule. Sadly, some
of the libraries indirectly depent on itself, like in the following
example:
lib LIB_A : a.cpp : : : <library>LIB_B ;
lib LIB_B : b.cpp : : : <library>LIB_C ;
lib LIB_C : c.cpp : : : <library>LIB_A ;
Boost.Build does not like this and does not want to compile.

Is there any way to trick Boost.Build into working with cyclic dependencies?
While googling for this problem, I read something about a workaround
with "alias" but it was not said how exactly this can be done.

Some additional questions:

In my special case I put the libraries into the "usage-requirements"
via an indirect conditional requirement like this:
lib LIB_A : a.cpp : : : <conditional>@NeededDependencies ;
I hope, this does not complicate the problem!?

Because I also want to automatically have some preprocessor-defines
when compiling a library I am also using the use-feature like this:
lib LIB_A : a.cpp : <use>LIB_B : : <define>USE_LIB_A <library>LIB_B ;
lib LIB_B : b.cpp : <use>LIB_C : : <define>USE_LIB_B <library>LIB_C ;
lib LIB_C : c.cpp : <use>LIB_A : : <define>USE_LIB_C <library>LIB_A ;
So, I expect all three makros "USE_LIB_*" to be defined for every
library when compiling. Is this correct (assuming Boost.Build could be
tricked into working with cyclic redundancies)?

Thanks for your help.
DENIZ
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

From forum: Boost - Build

Re: [filesystem]: infinite-recursion with symlink

2009-11-24T14:03:38Z

On Tue, Nov 24, 2009 at 10:16 AM, Zachary Turner <divisortheory@...>wrote:

> On Tue, Nov 24, 2009 at 7:35 AM, Beman Dawes <bdawes@...> wrote:
>
> > > And a second question: I didn't find anything about permission-handling
> -
> > > are there any plans? In my eyes, this is something essential
> > > for a filesystem-library.
> > >
> >
> > Not at the moment. We haven't figured out how to abstract away the
> > differences between POSIX and Windows approaches to permissions. Any
> ideas
> > appreciated.
> >
>
> I'm not sure there really is a way, because the two methods are not
> functionally equivalent, and in fact are quite different. i.e. windows
> ACLs
> can represent permissions that are not semantically representable in the
> unix model.

Cygwin attempts to map the traditional Posix permissions functionality onto
Windows. With Cygwin 1.7, now in beta, they are also mapping ACL's onto
Windows. While that approach may not supply all the features of Windows, it
does seem to provide enough functionality to be useful.

> In the filesystem library I've developed in-house my plan for
> implementing permissions is to just make a typedef called something like
> filesystem::permissions that resolve to opaque structures on both
> platforms,
> and then have APIs like filesystem::windows::allow_permission(),
> filesystem::windows::set_owner(), filesystem::posix::user_permissions(read
> |
> write | group), etc.
>

Boost.Filesystem has always resisted doing that. There is still
functionality other functionality that has been requested I'd like to work
on first.

>
> Is this Filesystem V3 going to support any of the following (and is there
> an
> estimated release date, even if it's highly speculative)?
>

The V3 library code is about ready for a beta. I'm working on docs now. I'm
semi-aiming for a January 1st beta release.

>
> a) timestamp operations
>

Which specific timestamp operations do you need? Last write time is already
supported.

> b) cross-platform create/open of files
>

Nothing planned, beyond the current <fstream> support.

> c) windows junctions and symlinks
>

Supported in V3.

> d) unix block/char devices, sockets, and pipes
>

Nothing planned in Boost.Filesystem. Several other Boost libraries already
have at least some support for these.

>
> create/open is the biggest gaping hole in the current FS library in my
> opinion. you often just need a handle and want to customized the way in
> which it's opened. with my code you can do soemthing like:
>
> filesystem::handle handle; /* opaque structure, only understood by the
> filesystem api */
> filesystem::object_info info; /* boost variant, internal type depends on
> type of filesystem object */
>
> filesystem::create_file(
> path,
> link_open_target, /* follow symlinks */
> only_dir, /* fail unless this is a directory handle
> */
> flags::async | flags::direct | flags::bypass_security, /*
> open for async direct i/o and disable any kernel security checking */
> &handle, /* have the function return the handle (this
> can be null if not interested) */
> &info; /* have the function return object info
> (this can be null if not interested) */
> );
>
> handle then is an opaque object that can be used by other filesystem apis
> like timestamp operations etc, and info is a boost::variant whose type
> depends on whether it's a directory, junctino, symlink, pipe, etc.
>

Nothing like that planned at the moment.

I've solved all of the above problems in a cross-platform way in my own
> in-house api but it might be difficult to integrate any of what i've done
> into an interface consistent with the current filesystem library. if you
> want any of this code though let me know.
>

What I'd be most interested in is motivation and use cases. I need to better
understand the need before I start thinking about code.

Thanks,

--Beman
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: Review Queue Needs Attention

2009-11-24T13:58:49Z

Am Tuesday 24 November 2009 22:46:21 schrieb Simonson, Lucanus J:

> I would recommend that authors try find a review manager before they
> request a review. If no one is interested in being the review manager of a
> given library then it might be that the author mistook polite interest for
> serious interest in the determining interest phase. We can easily fix the

I don't think the fact alone that noone is currently willing to perform some
unappealing bureaucratic work (being a review manager) shows a lack of
interest in a library.
judging by the review schedule (almost no review managers), that would mean
boost isn't very interested in new libraries in general.

http://www.boost.org/community/review_schedule.html
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

Re: Review Queue Needs Attention

2009-11-24T13:46:21Z

strasser@... wrote:

> Zitat von Tom Brinkman <reportbase@...>:
>
>> The number of review requests is
>> far outstripping the number of volunteer review managers.
>
> is the lack of review managers the bottleneck of the review process
> right now?
>
> I`m relatively new to boost, but judging from the "notes for review
> managers" on the website that doesn`t sound like a lot of work.
> I'm planning to submit a library for review myself, and the prospect
> that that'd take 2 years isn't very encouraging, so I'd probably
> volunteer just for this reason alone.
>
> maybe you could regularily post a call for review managers to the
> mailing list, with a list and a short description of libraries in need
> of a review manager?
>
> btw, I sent a request for sandbox access to boost-owner recently, to
> upload a preview of my library to the sandbox.
> does that take a while or has the process of requesting access
> changed? I haven't received anything so far.

I would recommend that authors try find a review manager before they request a review. If no one is interested in being the review manager of a given library then it might be that the author mistook polite interest for serious interest in the determining interest phase. We can easily fix the problem of lack of review managers for proposed libraries by making it clear that it is the author's responsibility to find a review manager for their library. The author of a proposed library should ideally become part of the boost community. That process should start before the library is accepted, not after, and it is through that process that the author finds a review manager.

Regards,
Luke
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

handling unicode strings / encodings?

2009-11-24T13:45:51Z

Hi,

I wonder what the state of handling unicode strings is in C++ / with
boost? I've found some references to the codecvt<> feature, and also
I've found utf8_codecvt_facet among the boost sources, but I can't
really make it work.

what I would need is to handle strings based on the whole unicode
representation, and to encode them to UTF-8 and back.

is there anything related in boost?

Akos
_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

Re: issues with setting properties on reverse graph

2009-11-24T13:35:57Z

On Tue, 24 Nov 2009, Mangal wrote:

>
>
> so this is what I see is happening
>
> if I use get_property(graph, propertyname) = propertyvalue
> to set the property on the graph then setting the property on reverse graphs
> does not work (even with the new typedef in the sample code i posted)
>
> however using set_property(graph, propertyname, propertyvalue) works when
> used with the new typedef.
> (even in my application)
>
> Thanks Jeremiah

Please try r57910; that should fix the get_property() issue.

-- Jeremiah Willcock
_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

Re: BGL: counting connected components subgraph

2009-11-24T13:34:52Z

Thanks for explanation,

If you just want to know the number of connected components define
your own predecessor_map for kruskal_minimum_spanning_tree. Then you
can count the vertices with themselves as predecessor. These vertices
are the roots of the spearate trees:

How to walk over those separate trees?

Is it should be something like this?

Graph::vertex_iterator vi, vi_end;
for(tie(vi, vi_end) = vertices(graphMST); vi != vi_end; ++vi)
if(*vi == pred[get(vi_map, *vi)])
num_components++;

else

{

WriteOutTree(num_components);??? ///

}

_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

Expat link settings [bug 3300]

2009-11-24T13:28:17Z

Could someone with more experience with Windows build issues take a look
at bug 3300 (https://svn.boost.org/trac/boost/ticket/3300) and determine
the best way to fix it? Is find-shared-library supposed to find libexpat,
not just expat? Thank you for your help.

-- Jeremiah Willcock
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

From forum: Boost - Build

Re: issues with setting properties on reverse graph

2009-11-24T13:26:45Z

so this is what I see is happening

if I use get_property(graph, propertyname) = propertyvalue
to set the property on the graph then setting the property on reverse graphs does not work (even with the new typedef in the sample code i posted)

however using set_property(graph, propertyname, propertyvalue) works when used with the new typedef.
(even in my application)

Thanks Jeremiah

in the first example that i posted i made the following change to the definition of reverse_graph

typedef reverse_graph<graph_t, graph_t&> reverse_graph_t;
and now setting the name property on reverse graph works. accessing it using the original graph also works.

However in my app which uses a new property defined by me the new typedef still throws at runtime
I will work with it a little more and if I can't figure it out will let you know

Thanks for the help

Jeremiah Willcock wrote:

On Tue, 24 Nov 2009, Mangal wrote:

>
> yes it works when I set it on the original graph.
> setting it in the original graph and reading in reverse_graph works. (which
> is what I do in my application)
>
> I had a function
> template<Graph>
> void myfun( Graph & g)
> {
> //some code
> get_property(g, graph_MyProperty) = propertyValue
> }
>
> and wanted to use it like
> myfun(originalGraph)
> myfun(reverseGraph)
>
> setting property on the reverse_graph does not seem to be doing anything,
> infact when trying to access the property somewhere else throws a null
> reference exception

Could you please try building your reverse_graph as:

reverse_graph<Graph, Graph&>

and see if that changes the behavior?

-- Jeremiah Willcock
_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

[function] Using boost::function when rtti is not available

2009-11-24T13:22:42Z

Hi,

Reposting this from the user mailing list, as it generated no comments.

I am in a gaming build environment that has traditionally turned off rtti because of space and portability issues.

But, I would like to use the very useful boost::function. On MSVC boost::function works, but fails on g++ for the ps3. I have read on the lists that it is possible to implement a rtti-less version, and that this is even wanted in the future.

See: http://article.gmane.org/gmane.comp.lib.boost.devel/192378
And http://article.gmane.org/gmane.comp.lib.boost.devel/191945

I know of a lot of people that would like this dependency on rtti removed.

My question to the list is: did anyone have a try at an implementation and could share it ? I have toyed with boost::function and sp_typeinfo.hpp and tried to replace occurrences of type_info in function_base.hpp, but I don't have enough understanding to finish the work and my early attempts have failed. As my current understanding goes, the function type could be generated with the sp_typeinfo trick. Is the sp_typeinfo.hpp route a viable one ?

Thank you,

David.
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

From forum: Boost - Dev

How to get rid of compiler version in library names?

2009-11-24T13:20:57Z

Hi,

I just installed Boost and noticed the library names all have the compiler/boost version in the file name, e.g. gcc41.
libboost_date_time-gcc41-mt-1_39.a

The program I'm trying to compiler only looks for the library name, e.g. libboost_date_time-mt.a.
My error:
error: Unable to find file or target named
error: '/usr/lib/libboost_date_time-mt.a'
error: referred from project at
error: '.'

How can I make boost install using the library names without compiler name/boost version?

Thanks!

From forum: Boost - Users

Re: issues with setting properties on reverse graph

2009-11-24T13:17:05Z

in the first example that i posted i made the following change to the definition of reverse_graph

typedef reverse_graph<graph_t, graph_t&> reverse_graph_t;
and now setting the name property on reverse graph works. accessing it using the original graph also works.

However in my app which uses a new property defined by me the new typedef still throws at runtime
I will work with it a little more and if I can't figure it out will let you know

Thanks for the help

Jeremiah Willcock wrote:

On Tue, 24 Nov 2009, Mangal wrote:

>
> yes it works when I set it on the original graph.
> setting it in the original graph and reading in reverse_graph works. (which
> is what I do in my application)
>
> I had a function
> template<Graph>
> void myfun( Graph & g)
> {
> //some code
> get_property(g, graph_MyProperty) = propertyValue
> }
>
> and wanted to use it like
> myfun(originalGraph)
> myfun(reverseGraph)
>
> setting property on the reverse_graph does not seem to be doing anything,
> infact when trying to access the property somewhere else throws a null
> reference exception

Could you please try building your reverse_graph as:

reverse_graph<Graph, Graph&>

and see if that changes the behavior?

-- Jeremiah Willcock
_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users

Re: issues with setting properties on reverse graph

2009-11-24T12:58:03Z

On Tue, 24 Nov 2009, Mangal wrote:

>
> yes it works when I set it on the original graph.
> setting it in the original graph and reading in reverse_graph works. (which
> is what I do in my application)
>
> I had a function
> template<Graph>
> void myfun( Graph & g)
> {
> //some code
> get_property(g, graph_MyProperty) = propertyValue
> }
>
> and wanted to use it like
> myfun(originalGraph)
> myfun(reverseGraph)
>
> setting property on the reverse_graph does not seem to be doing anything,
> infact when trying to access the property somewhere else throws a null
> reference exception

Could you please try building your reverse_graph as:

reverse_graph<Graph, Graph&>

and see if that changes the behavior?

-- Jeremiah Willcock
_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

From forum: Boost - Users