December 2012 - Boost - lists.preview.boost.org

[trac] Add new components
by Michel Morin 10 Dec '12

10 Dec '12

The following four libraries do not have "components" in trac (lockfree already has the component in trac): - atomic - coroutine - multiprecision - odeint (numeric/odeint) Regards, Michel

4 4

[algorithm][hex] function hex_char_to_int in unnamed namespace in header file
by Felipe Magno de Almeida 10 Dec '12

10 Dec '12

Hello, AFAIK, unnamed namespaces are dangerous in headers. There is a commentary just above the function definition: // this needs to be in an un-named namespace because it is not a template // and might get included in several compilation units. This could cause // multiple definition errors at link time. But it seems the better thing would be to define it inline. It is exactly because it can be used in several translation units that it can cause an ODR violation if defined in a unnamed namespace AFAIK. Regards, -- Felipe Magno de Almeida

3 8

Boost new library policy
by islam y. yasar 10 Dec '12

10 Dec '12

Hi Boost Developers; i and my friend want to develope a library for boost. Is there any policy document for that ? i want to learn this process step by step. thank you.

6 9

[boost::asio] SCTP support with boost::asio
by Ajay Yadav 10 Dec '12

10 Dec '12

Hi, I am newbie to the boost library. I would like to develop the SCTP client-server application. Is boost::asio supported SCTP. Please guide me how I can make the application using SCTP. Regards, Ajay Yadav DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . -----------------------------------------------------------------------------------------------------------------------

2 1

[quickbook] template vs block vs phrase issues
by Andreas Pokorny 09 Dec '12

09 Dec '12

Hi, I use quickbook to write software design documentation targeting pdf. We now introduce a requirements tracking system that includes both source code and design documents. To describe or refer to requirements in docbook docments special xml markup is needed. I.e. something like <reqfooo><status>approved</status><version>1</version><id>DoOnlyNeededStuff</id><description></description></regfoo>. Since I do not want to write XML I added quickbook templates: [template reqfoo[id contents]'''<reqcfoo><id>'''[id]'''</id>'''[contents]'''</reqfoo>'''] [template sdesc[contents]'''<shortdesc>'''[contents]'''</shortdesc>'''] [template verification[contents]'''<verifycrit>'''[contents]'''</verifycrit>'''] [template source[contents]'''<source>'''[contents]'''</source>'''] [template usecase[contents]'''<usecase>'''[contents]'''</usecase>'''] [template status[contents]'''<status>'''[contents]'''</status>'''] [template version[contents]'''<version>'''[contents]'''</version>'''] and finally: [template desc[contents]'''<description>'''[contents] '''</description>'''] Now I want to use block elements inside the contents parameter of desc. Is there any way to achieve that? The only thing I can think of is: [template desc[]'''<description>'''] [template enddesc[]'''</description>'''] But then quickbook is just as good as xml! I tried to make desc a block level template by adding a line break at different positions, but then I get broken xml code, since para tags are spread around <description> regards Andreas

2 5

[Git] Modularizing Boost libraries with sublibs
by Daniel Pfeifer 09 Dec '12

09 Dec '12

While adding Boost.ODEint to the modularization manifest, I realized some inconsistencies about sublibs. The directories in "libs" usually contain one library each. In this case, we move the content to a dedicated Git repository. Some directories however (algorithm, numeric) host multiple libraries. How should we treat them? Move each one to a dedicated Git repository, or leave them grouped together? What's currently inconsistent, is that "numeric" is split into individual repositories, while "algorithm" is not. Further, I saw that the Git submodules of numeric's sublibraries are generated in "libs" rather than "libs/numeric", which is wrong. However, before I fix it, we need to decide whether these individual submodules should be individual or not. Opinions? Cheers, Daniel

4 5

Re: [boost] [Git] tools/wave missing (was: Documentation for Git and Modular Boost conversion)
by Hartmut Kaiser 09 Dec '12

09 Dec '12

> On Fri, Dec 7, 2012 at 3:42 PM, Eric Niebler <eric(a)boostpro.com> wrote: > > On 12/7/2012 11:44 AM, Oliver Kowalke wrote: > > >> Do I have to clone an additional submodule (which is not mentioned in > >> the docu)? > > > > Beman's docs appear to lack instructions for how to clone the > > super-project and initialize the sub-modules. That would be a nice > > addition. I don't know the steps and can't find them ATM, but I know > > it's documented *somewhere*. Beman? > > Just added: https://svn.boost.org/trac/boost/wiki/TryModBoost > > The original instructions were buried in a C++Now presentation slide. When I follow those steps as far as I can see everything looks fine except for tools/wave, which is missing. Is that intentional? Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu > > Thanks, > > --Beman > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

2 2

[Smart Pointers]
by Rahul Sr 09 Dec '12

09 Dec '12

Hi All, This is my first post though so please bear with my sentences. I have used scoped_ptr but this is too tied with new/delete semantics i.e. can't use it with pointers which gets allocated from specialized memory area. class AManager { public: A * allocate(); void deallocate(A * p); }; class A { ..... }; This specially happens when I use scoped pointer for C like pointers/allocator: Can I modify scoped pointer to have release semantics which is user defined: template<typename T> class DefaultReleasePolicy { static void releaseA(T * p) { delete p; } }; class ReleaseAPolicy { static void releaseA(A * p) { AManager::getInstance()->deallocate(p); } }; template<typename T,typemame ReleasePolicy = DefaultReleasePolicy<T> > class ScopedPtrModified { ~ScopedPtrModified() { ReleasePolicy::release(m_ptr); } }; Is this fine? Let me know your thoughts. Regards, Rahul

3 3

[odeint] Request to merge odeint into release branch
by Karsten Ahnert 09 Dec '12

09 Dec '12

I would like to ask for permission to merge odeint into the release branch. There are currently four failures in the regression tests. Two have already been fixed. The other two originate from the build time out of 180 seconds. These two tests will often require longer build times, since they heavily use Boost.Fusion, Boost.Units and Boost.MPL.

2 5

[multiprecision] Request permision to merge to release.
by John Maddock 09 Dec '12

09 Dec '12

I'd like to ask permission to merge the multiprecision lib to release. Note that as things stand I'm still chasing down test failures, but these are now mostly down to: * Things that work locally, but the testers haven't cycled yet. * 300s timeouts - mostly from the intel compiler :-( Aside: in an effort to reduce the number of timeouts, I've basically gutted some of the tests when the compiler is Intel, and I think I have all the build times under 20s on my Linux box, yet I'm still getting 300s timeouts on some tester machines, either those machines are seriously underpowered or I'm missing something here :-( Cheers, John.

3 5