- Boost - lists.preview.boost.org

[itl] status?
by Jeff Flinn 03 Sep '10

03 Sep '10

What is the current status of the interval template library? Where can I get the latest version? Thanks, Jeff

4 3

nvcc config and mpl_assert
by Andrey Asadchev 03 Sep '10

03 Sep '10

recent boost distribution introduced nvcc as compiler which results in failed compilation when using mpl assert (and components of mpl which do so) here is the fix (it produces warnings, but allows for compile) --- config/compiler/nvcc.hpp 2010-09-02 18:43:46.000000000 -0500 +++ config/compiler/nvcc.hpp~ 2010-09-02 16:40:32.000000000 -0500 @@ -17,8 +17,8 @@ // Boost support macro for NVCC // NVCC Basically behaves like some flavor of MSVC6 + some specific quirks -//#define BOOST_NO_INCLASS_MEMBER_INITIALIZATION -//#define BOOST_MSVC6_MEMBER_TEMPLATES +#define BOOST_NO_INCLASS_MEMBER_INITIALIZATION +#define BOOST_MSVC6_MEMBER_TEMPLATES #define BOOST_HAS_UNISTD_H #define BOOST_HAS_STDINT_H #define BOOST_HAS_SIGACTION --- mpl/aux_/config/gcc.hpp 2010-09-02 18:49:14.000000000 -0500 +++ mpl/aux_/config/gcc.hpp~ 2010-09-02 19:03:39.000000000 -0500 @@ -14,7 +14,7 @@ // $Date: 2008-10-11 02:19:02 -0400 (Sat, 11 Oct 2008) $ // $Revision: 49267 $ -#if defined(__GNUC__) && !(defined(__EDG_VERSION__) || defined(__CUDACC__)) +#if defined(__GNUC__) && !defined(__EDG_VERSION__) # define BOOST_MPL_CFG_GCC ((__GNUC__ << 8) | __GNUC_MINOR__) #else # define BOOST_MPL_CFG_GCC 0 I think nvcc compiler must be differentiated whenever it uses Microsoft (Windows) or GCC(linux) compiler

2 1

[Locale] MS-LCID's table from MSDN site and Copyrights
by Artyom 03 Sep '10

03 Sep '10

Hello, I need a table for conversion of Windows LCIDs to ISO-639 Language and ISO-3199 Country codes and back. I need this for creation Win32 API based backend for Boost.Locale and ability to convert locale names like en_US to LCID 0x0409. Such table can be found here (link to PDF of this page): <http://msdn.microsoft.com/en-us/library/cc233965.aspx> It contains all I need. Now I want to insert such table to the cpp file and include it to the Boost.Locale library. I've read the Copyright notice on this page but I don't clearly understand: - Can I do this? It seems that this notice allow to copy the data but not sure. - Can I release a file that includes such table under Boost License? I need some advice from people who had already deal with such documents or stuff like this or know to read "lowers language" a little bit better and point me to specific line that would make it clear for me. Thank you Artyom P.S.: I can create a workaround based on iterating over all installed LCID's in runtime and querying their ISO-639 and ISO-3199 codes using GetLocaleInfo first time I need to use such table, but integrating static table would be much simpler and faster solution.

3 3

Re: [boost] Thoughts for a GUI (Primitives) Library
by Ralf Globisch 02 Sep '10

02 Sep '10

>>> Giorgio Zoppi 09/01/10 2:17 PM >>> I don't know if there's enough space for this. There are a plenty of GUIs Framework, like Qt or wxWindows, which are more advanced. -- Quiero ser el rayo de sol que cada día te despierta para hacerte respirar y vivir en me. "Favola -Moda". I concur, it would be difficult to match QT for any cross platform GUI development. It is an extensive, mature framework available under the LGPL and in terms of boost there are workarounds to make boost and QT signals co-exist. I'm not so familiar with wxWindows, but both of these GUI libs have been under development for some time and it would be difficult to compete with them, which is what any new library would have to do. -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support.

14 19

Re: [boost] [msm] on_entry must be implemented for every initial events for every states in substatemachines.
by Christophe Henry 02 Sep '10

02 Sep '10

> Hi All > > In the following little example see attachment, > I have a problem that in the RunningStateMachine::State2 the on_entry > function must be implemented with event1 and with event3 as well > but from the logic point of view there is no possibility to call > on_entry in RunningStateMachine::State2 with event1. > > actually at runtime there is no call is happening to to the function : > void on_entry(event1 const&,FSM& ) {std::cout << "entering: > State2:Event1" << std::endl;} > but it must be defined and even implemented ( if no implementation > provided linker error occurs). > Is it a restriction/bug or I'm missing something ? > It is only happening with initial events for substatemachines ? > Or is there a kind of pattern to know what events can enter exit a > state in a top of the ones present in the transition tables ?. Hi, Well, we don't want to go into the implementation details (we really don't ;-) ) but to make it short, msm tries the entry event with every state to see which state is active at run-time. And this means that every state's entry and exit behavior must be able to process this event. Of course it'd be possible to know in advance that some states are wrong candidates but this requires some compile-time graph analysis. And I do plan to start working on this using the metagraph library which is in construction. But for the moment I don't have this tool in msm. And even when I do, there will be a compile-time cost. Back to the example, when you write: template <class FSM> void on_entry(event3 const&,FSM& ) {std::cout << "entering: State2:Event3" << std::endl;} You are hiding the default on_entry, which provides you with an empty implementation for all events. The solution is not incredibly beautiful but will save us some compile-time. We need to tell the compiler we have a version for event3 and one for all others: template <class Event,class FSM> typename boost::enable_if< typename boost::is_same<Event,event3>::type,void >::type // version for event3 on_entry(Event const&,FSM& ) {std::cout << "entering: State2:Event3" << std::endl;} template <class Event,class FSM> typename boost::disable_if< typename boost::is_same<Event,event3>::type,void >::type // version for events != event3 on_entry(Event const&,FSM& ) {std::cout << "entering: State2:Event1" << std::endl;} Now it compiles :) HTH, Christophe

1 0

[quickbook] QUICKBOOK_CYGWIN_1_5 undefined
by vicente.botet 02 Sep '10

02 Sep '10

Hi, I have moved to v1.44, and while I try to build quickbook on cygwin-1.5 I get the following error $ bjam ...patience... ...found 1304 targets... ...updating 5 targets... gcc.compile.c++ ../../../bin.v2/tools/quickbook/gcc-3.4.4/debug/link-static/deta il/input_path.o C:\cygwin\boost\v44\tools\quickbook\detail\input_path.cpp: In function `void qui ckbook::detail::validate(boost::any&, const std::vector<std::string, std::alloca tor<std::string> >&, quickbook::detail::input_path*, int)': C:\cygwin\boost\v44\tools\quickbook\detail\input_path.cpp:80: error: `cygwin_con v_path_t' undeclared (first use this function) C:\cygwin\boost\v44\tools\quickbook\detail\input_path.cpp:80: error: (Each undec lared identifier is reported only once for each function it appears in.) C:\cygwin\boost\v44\tools\quickbook\detail\input_path.cpp:80: error: expected `; ' before "flags" C:\cygwin\boost\v44\tools\quickbook\detail\input_path.cpp:87: error: `flags' und eclared (first use this function) C:\cygwin\boost\v44\tools\quickbook\detail\input_path.cpp:87: error: `cygwin_con v_path' undeclared (first use this function) "g++" -ftemplate-depth-300 -O0 -fno-inline -Wall -g -g0 -DBOOST_ALL_NO_LIB= 1 -DBOOST_SYSTEM_STATIC_LINK=1 -I"../../.." -c -o "C:\cygwin\boost\v44\bin.v2\t ools\quickbook\gcc-3.4.4\debug\link-static\detail\input_path.o" "C:\cygwin\boost \v44\tools\quickbook\detail\input_path.cpp" ...failed gcc.compile.c++ ../../../bin.v2/tools/quickbook/gcc-3.4.4/debug/link-s tatic/detail/input_path.o... ...skipped <p../../../bin.v2/tools/quickbook/gcc-3.4.4/debug/link-static>quickbo ok.exe for lack of <p../../../bin.v2/tools/quickbook/gcc-3.4.4/debug/link-static >detail/input_path.o... See on the code I see that there is a test on QUICKBOOK_CYGWIN_1_5 which is not defined in any file. When I define it everything works as before. Should the user define QUICKBOOK_CYGWIN_1_5 when working on cygwin-1.5 ? Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

2 3

Re: [boost] [msm] on_entry must be implemented for every initial events for every states in substatemachines.
by Christophe Henry 02 Sep '10

02 Sep '10

> Hi All > > In the following little example see attachment, > I have a problem that in the RunningStateMachine::State2 the on_entry > function must be implemented with event1 and with event3 as well > but from the logic point of view there is no possibility to call > on_entry in RunningStateMachine::State2 with event1. > > actually at runtime there is no call is happening to to the function : > void on_entry(event1 const&,FSM& ) {std::cout << "entering: > State2:Event1" << std::endl;} > > but it must be defined and even implemented ( if no implementation > provided linker error occurs). > > Is it a restriction/bug or I'm missing something ? > It is only happening with initial events for substatemachines ? > Or is there a kind of pattern to know what events can enter exit a > state in a top of the ones present in the transition tables ?. > > Br. > Richie Hi, I don't find this entry function or a State2. Am I missing something or did you attach the wrong file? Regards, Christophe

2 2

Re: [boost] [msm] Boost MPL vector limit size exceeded
by Christophe Henry 01 Sep '10

01 Sep '10

Hi, Sorry for my late answer. > while building a state machine that also includes submachines, we exceeded > the possible max number of MPL vector entries (which is to 50 to my > knowledge) for transition tables. > Is there an easy way to solve that? > How to increase the max possible number of MPL vector entries? > > Do I have to manually create vector60.hpp and vector60_c.hpp? Or is there > something that generates all those files (also for larger vectors)? > > I also tried the define "BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS" with and > without specifing the define "FUSION_MAX_VECTOR_SIZE". > I tried the "favor_compile_time" vs "favor_runtime_speed" as well. > In both cases the MPL vector size was to small. I personally defined myself headers up to 100. It's pretty easy actually. I didn't try the scripts. Erik Nelson wrote: >I used the #defines > >BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS >BOOST_MPL_LIMIT_VECTOR_SIZE=60 > >For my whole project and it worked for me. I wasn't using MSM, though I just tried it and it seems to work. Thanks Erik :) BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS will only help you up to 50. FUSION_MAX_VECTOR_SIZE is only to increase the number of states defined in a state machine (under the hood, a fusion::set is used to contain all the states). > Does it actually mean, in case we use submachines, that MSM generates a > flat transition table including everything in one MPL vector? > Example: > Main state machine consiting of 10 transitions + 1 submachine consiting of > 5 transitions. > Do we than have a transition table with around 15 entries that are stored > somehow in an MPL vector of size 15? You should get a look at http://www.boost.org/doc/libs/1_44_0/libs/msm/doc/HTML/ch05.html MSM generates an entry inside the main table for every event found in the submachines. This avoids forwarding events which a submachine will never be able to process (performance improvement). Juraj Ivančić wrote: >Finally I gave up and used the kludge described in the post referenced >above. Meanwhile I managed to trim down the number of transitions in my >state machine and got back into vector50 bounds. I also think that you might want to see if you can reduce the number of transitions if you can, because soon the compile-time will start hurting. Regards, Christophe

2 1

[gil] Who has a big-endian machine?
by Christian Henning 01 Sep '10

01 Sep '10

Hi there, could someone with a big-endian machine run the following code with the latest gil code from the trunk? #include <cassert> #include <vector> #include <boost/gil/gil_all.hpp> using namespace boost; using namespace gil; int main() { typedef bit_aligned_image1_type< 3, gray_layout_t >::type gray3_image_t; typedef gray3_image_t image_t; typedef image_t::view_t view_t; typedef view_t::reference ref_t; typedef bit_aligned_pixel_iterator< ref_t > iterator_t; std::vector< unsigned char > buf( 4 ); // bit pattern is: 1011 0110 0110 1101 1101 1011 // each byte is read right to left buf[0] = 182; buf[1] = 109; buf[2] = 219; iterator_t it( &buf[0], 0 ); ref_t p1 = *it; it++; ref_t p2 = *it; it++; ref_t p3 = *it; it++; ref_t p4 = *it; it++; ref_t p5 = *it; it++; ref_t p6 = *it; it++; ref_t p7 = *it; it++; ref_t p8 = *it; it++; unsigned char v1 = get_color( p1, gray_color_t() ); unsigned char v2 = get_color( p2, gray_color_t() ); unsigned char v3 = get_color( p3, gray_color_t() ); unsigned char v4 = get_color( p4, gray_color_t() ); unsigned char v5 = get_color( p5, gray_color_t() ); unsigned char v6 = get_color( p6, gray_color_t() ); unsigned char v7 = get_color( p7, gray_color_t() ); unsigned char v8 = get_color( p8, gray_color_t() ); // all values should be 110b ( 6 ); assert( v1 == 6 ); assert( v2 == 6 ); assert( v3 == 6 ); assert( v4 == 6 ); assert( v5 == 6 ); assert( v6 == 6 ); assert( v7 == 6 ); assert( v8 == 6 ); return 0; } Thanks ahead, Christian

2 1

Re: [boost] [gsoc] Boost.Process done
by Adam Merz 01 Sep '10

01 Sep '10

Boris Schaeling <boris <at> highscore.de> writes: <snip> > If there are other ideas how to generate a unique name I can update the code > (Windows provides an API to generate UUIDs but unfortunately it requires COM; > on POSIX systems I'm not aware of any system function which could generate > UUIDs). > > Boris For Windows, Neither UuidCreate nor UuidCreateSequential require COM. Are these not generally suitable for your needs?

3 5

[function_types]howto rebuild components_impl/arityXX_Y.hpp?
by Larry Evans 01 Sep '10

01 Sep '10

trunk/boost/function_types/detail/components_impl has several arityXX_Y.hpp files which use vectorN templates. I want to replace vectorN with just vector. >From looking at libs/function_types/build/Jamfile, I guessed that replacing that with the attached Jamfile and attached master.hpp file would do the job; however, All I get is: [CUT_HERE] -*- mode: compilation; default-directory: "~/prog_dev/boost-svn/ro/boost_1_44_0/sandbox/rw/variadic_templates/libs/function_types/build/" -*- Compilation started at Wed Sep 1 13:01:38 bjam sh: icpc: not found BOOST_ROOT=/home/evansl/prog_dev/boost-svn/ro/boost_1_44_0 ...found 1 target... Compilation finished at Wed Sep 1 13:01:40 {/CUT_HERE] How do I replace vectorN with vector in the arityXX_Y.hpp files? -regards, Larry

1 0

[phoenix3] Conflict with fusion::at and stl::at
by Denis Taniguchi 01 Sep '10

01 Sep '10

Hi, The following code doesn't seem to compile, with phoenix3 trunk (revision 65168): #include <boost/phoenix/stl/container.hpp> #include <boost/phoenix/fusion/at.hpp> int main() { return 0; } Since it's a design issue (both fusion::at and stl::at are visible in boost::phoenix), I'm not submitting a patch. Best regards, Denis

1 0

Re: [boost] Is Boost-CMake Dead or Alive?
by Vladimir Prus 01 Sep '10

01 Sep '10

Eric Niebler wrote: [moving to -devel, where it really belongs] > On 8/28/2010 3:12 AM, Vladimir Prus wrote: >> David Abrahams wrote: >>> At Thu, 26 Aug 2010 13:41:46 -0400, Eric Niebler wrote: >>>> >>>> Even if we achieve our vision, it's not clear that Boost as an >>>> organization will adopt it. >>> >>> <ahem> >>> >>> A small correction: even *when* we achieve our vision, there's no >>> *guarantee* that Boost will adopt it. >>> >>> [But Boost will adopt it. Just promise not to sue us in case they >>> don't :-)] >> >> I find the above statement to be a very interesting advertisement approach >> for a project that addresses requirements that were never discussed on >> this list, and which itself was never discussed much. In fact, this statement >> sounds like you have made some secret arrangements (*), or even that you had >> some revelation from supernatural powers -- which is probably not what you >> was going to communicate. >> >> I think Eric statement is much more balanced. >> >> - Volodya >> >> (*) In fact, ryppl gave an impression of some secret arrangements from the >> very start. > > Dave was expressing confidence about the value of our work, no more. > There have been no secrets and no back-room negotiations. Eric, unfortunately, I must have been taught either wrong English or wrong logic, because surely "I am confident that XXX will YYY" conveys quite a different meaning than "XXX will YYY". While now and here, you can clarify the meaning, I doubt you'll be around when any given person reads such statements in his email client. And of course, when a representative of a third party having commercial interest in the matter makes public statements to the effect "XXX will YYY" (without any "I am confident" qualifier (*), this surely makes the matter look even more suspicious. > Boost's > scalability problems have been discussed endlessly here and in open > sessions at BoostCon, I think "endlessly" is a very accurate word here. The discussions have failed to clarify, prioritize, or even list the issues. Say, recently Dave has announced that he'll no longer maintains his libraries (**) because SVN is slow and library organization is a "mess". While other folks agree that there are some issues, they don't seem to have that drastic effects in general. That thread has died, and we still don't know why SVN performance (and other issues) is enough to make one person stop maintaining his libraries completely, while another person is happy to have extra latte while SVN does one-a-quarter merge to release branch. > but no decisions about Boost's future were made or > will be made by fiat. Boost doesn't work that way. > > It's true that the requirements of, or even the need for, ryppl was not > debated here on this list. But that's how most Boost libraries start. > Someone has a vision and builds a thing. Then they bring it to Boost and > it's improved and accepted or rejected. Trying to get quorum on a thing > that isn't built yet is just hard. "If you build it, they will come" -- > so we hope. It is clear that each project involves a vision (very hard to share), design (somewhat shareable) and review (share as you like). And it's perfectly fine to have a vision that involves fixing all issues with Boost development that you are aware of. However, saying "Boost will adopt ryppl, no we won't bother to even list the issues it will fix" sound bizarre -- because it's an attempt to share a vision -- which is not shareable. - Volodya (*) Check recent boost-cmake postings for an example. In fact, said party even has marketing materials which *already* mentions Boost. (**) http://old.nabble.com/Maintenance-suspended-td29100510.html

2 1

[PropertyTree] i18n Bug in the build-in rapidxml XML parser
by 卓强 ZHUO Qiang 01 Sep '10

01 Sep '10

Hi All, I have encounter an bug in Boost.PropertyTree and submit a patch to fix this bug 3 month ago: https://svn.boost.org/trac/boost/ticket/4340 Below is a brief description: ---------------------------------------------------------- boost::property_tree::read_xml(wistream&, wptree&) throw exception if tag/value/attribute has a unicode with '\0' inside, for example, for unicode char L'\u4E00', an exception will be throw because the parser treat L'\u4E00' as '\0'. The following test case reproduce the bug: BOOST_AUTO_TEST_CASE(test_i18n_xml_tag_name) { wistringstream in(L"<\u4E00>abc</\u4E00>"); property_tree::wptree pt; BOOST_REQUIRE_NO_THROW(property_tree::read_xml(in, pt)); BOOST_CHECK(L"abc" == pt.get<wstring>(L"\u4E00")); } ---------------------------------------------------------------- This ticket have been sleeping for 3 month, I'm wondering if someone could help review it and apply the patch to the trunk or just fix it in another way. More generally, what's the boost policy for maintain the existing library, especially regarding for the bug fix. Best Regards, Qiang http://zhuoqiang.me

1 0

[iostreams] filtering_ostream does not flush std::cout.
by Duncan Smith 01 Sep '10

01 Sep '10

I'm using Boost 1.43.0, and I've found that filtering_ostream does not flush "std::cout". I found a relevant (and recent) ticket against Boost 1.44.0, but my issue is slightly different. https://svn.boost.org/trac/boost/ticket/4590 I'm using GCC 4.3.4 on Gentoo Linux. I'm hoping that I'm just doing something wrong, but if you think there's a bug, I'll add my testcase to the ticket. The basic recipe: filtering_ostream out; out.push(any_filter_at_all()); out.push(std::cout); out << "Hello World!" << std::flush; sleep(10); // Observe an empty console. std::cout << std::flush; sleep(10); // Observe printed text on console. This problem is quite bad for me when doing the following on the command-line (for a more complicated program): ./program 2>&1 | tee some-file.log Because stdout is not getting flushed, the stdout and stderr get intermingled strangely. However, disabling buffering on stdout works around the problem: stdbuf --output=0 ./program 2>&1 | tee some-file.log Please tell me if you think there's a bug in my code. If it's a bug in Boost.Iostreams (or I'm expecting the wrong behaviour), I would appreciate any ideas for workarounds (I tried cout.setf(unitbuf), and that doesn't seem to do the trick). Here's the full text of my code: ------------------ // Test case for flushing a filtering_ostream based on the // boost_iostreams_filtering_ostream.cpp attached to ticket #4950: // https://svn.boost.org/trac/boost/ticket/4590 // https://svn.boost.org/trac/boost/attachment/ticket/4590/boost_iostreams_fil… // changed to use "cout" as the sink. // // Flushing a filtering_ostream using the flush() global function does not work // in Boost 1.43. I suspect it also does not work in Boost 1.44. // // Using GCC-4.3.4 on Gentoo Linux. // #include <cassert> #include <string> #include <boost/iostreams/categories.hpp> #include <boost/iostreams/operations.hpp> #include <boost/iostreams/filtering_stream.hpp> #include <iostream> // Included for "sleep()" call below. #include <unistd.h> namespace io = boost::iostreams; // Simple output filter forwarding just forwarding the put chars to // the sink. struct transparent_output_filter { typedef char char_type; typedef io::output_filter_tag category; template <typename Sink> bool put(Sink& snk, char c) { return io::put(snk, c); } }; int main(int argc, char *argv[]) { using namespace std; io::filtering_stream<io::output> out; // Transparent filter just forward the characters to the sink. // // Note: I observe this behaviour with and without this line. out.push(transparent_output_filter()); // Sink appends characters to "cout". out.push(cout); // Write test string to filtering_ostream. out << "Hello World!"; // On my system, this will flush the buffer iff I'm on an // interactive console. "\n" and endl have the same effect. I believe // that my shell sets "stdout" to be line-buffered if it's interactive. // out << "\n"; bool wasFlushed = false; // The flush does *not* work in Boost 1.43. wasFlushed = io::flush(out); // This assertion does not go off, though. assert(wasFlushed); // This also doesn't work. wasFlushed = out.flush(); assert(wasFlushed); // This also doesn't work. out << std::flush; // Demonstrate that none of the above flush calls had any effect on "cout". sleep(10); // Now we finally get the characters on the console. cout << flush; // Demonstrate that the direct flush call works when called directly on // "cout". sleep(10); return 0; }

1 0

[msm] on_entry must be implemented for every initial events for every states in substatemachines.
by Richard Szabo 01 Sep '10

01 Sep '10

Hi All In the following little example see attachment, I have a problem that in the RunningStateMachine::State2 the on_entry function must be implemented with event1 and with event3 as well but from the logic point of view there is no possibility to call on_entry in RunningStateMachine::State2 with event1. actually at runtime there is no call is happening to to the function : void on_entry(event1 const&,FSM& ) {std::cout << "entering: State2:Event1" << std::endl;} but it must be defined and even implemented ( if no implementation provided linker error occurs). Is it a restriction/bug or I'm missing something ? It is only happening with initial events for substatemachines ? Or is there a kind of pattern to know what events can enter exit a state in a top of the ones present in the transition tables ?. Br. Richie

1 0

Re: [boost] [msm] Boost MPL vector limit size exceeded
by Michael.Herchel＠rohde-schwarz.com 01 Sep '10

01 Sep '10

Hi, thanks for the answers. >> I also tried the define "BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS" >> with and without specifying the define "FUSION_MAX_VECTOR_SIZE". > I used the #defines > BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS > BOOST_MPL_LIMIT_VECTOR_SIZE=60 Sorry, this was a mistake. Of course I used "BOOST_MPL_LIMIT_VECTOR_SIZE" instead of "FUSION_MAX_VECTOR_SIZE"

1 0

[msm] Boost MPL vector limit size exceeded
by Michael.Herchel＠rohde-schwarz.com 01 Sep '10

01 Sep '10

Hi, while building a state machine that also includes submachines, we exceeded the possible max number of MPL vector entries (which is to 50 to my knowledge) for transition tables. Is there an easy way to solve that? How to increase the max possible number of MPL vector entries? Do I have to manually create vector60.hpp and vector60_c.hpp? Or is there something that generates all those files (also for larger vectors)? I also tried the define "BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS" with and without specifing the define "FUSION_MAX_VECTOR_SIZE". I tried the "favor_compile_time" vs "favor_runtime_speed" as well. In both cases the MPL vector size was to small. Does it actually mean, in case we use submachines, that MSM generates a flat transition table including everything in one MPL vector? Example: Main state machine consiting of 10 transitions + 1 submachine consiting of 5 transitions. Do we than have a transition table with around 15 entries that are stored somehow in an MPL vector of size 15? Thanks for your help, Michi

4 3

[Boost] [Log] Problem with Release mode build
by Sivaram Kannan 31 Aug '10

31 Aug '10

Hi, I have been using boost log with two of my projects, one an VC++ 2008 exe and another a VC++ DLL. Boost log was working as expected in the Debug mode. But when I compiled the projects in release mode, the boost log with the exe is not logging anything on the file and the dll is creating an access violation. Following is the call stack which is throwing the error. cnbc.dll!boost::log_mt_nt5::sources::basic_logger<wchar_t,boost::log_mt_nt5::sources::wseverity_logger_mt<int>,boost::log_mt_nt5::sources::multi_thread_model<boost::shared_mutex> >::open_record_unlocked<boost::parameter::aux::tagged_argument<boost::log_mt_nt5::keywords::tag::severity,enum severity const > >(const boost::parameter::aux::tagged_argument<boost::log_mt_nt5::keywords::tag::severity,enum severity const > & args={...}) Line 269 + 0x15 bytes C++ cnbc.dll!boost::log_mt_nt5::sources::basic_severity_logger<boost::log_mt_nt5::sources::basic_logger<wchar_t,boost::log_mt_nt5::sources::wseverity_logger_mt<int>,boost::log_mt_nt5::sources::multi_thread_model<boost::shared_mutex> >,int>::open_record_unlocked<boost::parameter::aux::tagged_argument<boost::log_mt_nt5::keywords::tag::severity,enum severity const > >(const boost::parameter::aux::tagged_argument<boost::log_mt_nt5::keywords::tag::severity,enum severity const > & args={...}) Line 226 + 0xc bytes C++ cnbc.dll!boost::log_mt_nt5::sources::basic_composite_logger<wchar_t,boost::log_mt_nt5::sources::wseverity_logger_mt<int>,boost::log_mt_nt5::sources::multi_thread_model<boost::shared_mutex>,boost::mpl::vector1<boost::log_mt_nt5::sources::severity<int> > >::open_record<boost::parameter::aux::tagged_argument<boost::log_mt_nt5::keywords::tag::severity,enum severity const > >(const boost::parameter::aux::tagged_argument<boost::log_mt_nt5::keywords::tag::severity,enum severity const > & args={...}) Line 509 + 0x14 bytes C++ I have compiled the boost in release mode and as shared. Following is the command I used. , .\bjam.exe --with-log --with-filesystem --with-system --with-date_time --with-thread --with-regex define=BOOST_ALL_DYN_LINK variant=release link=shared stage What am i doing wrong here?? Thanks, Siva. .

2 5

Re: [boost] Some modifications to the Boost random library
by Eric Hopper 31 Aug '10

31 Aug '10

Steven Watanabe wrote: > Eric Hopper wrote: >> I have written a new class for small random integers... >> >> Would there be interest in these modifications? > >Can you post the code here? Sure. I've attach the patch file against Boost 1.43. -- "It does me no injury for my neighbor to say there are twenty gods or no God. It neither picks my pocket nor breaks my leg." --- Thomas Jefferson "Go to Heaven for the climate, Hell for the company." -- Mark Twain -- Eric Hopper (http://www.omnifarious.org/~hopper) --

3 3

[website] documentation page shows 1.43.0 as current
by Michael Caisse 31 Aug '10

31 Aug '10

<http://www.boost.org/doc/> indicates 1.43.0 is the current release and no link exists for 1.44.0 michael -- ---------------------------------- Michael Caisse Object Modeling Designs www.objectmodelingdesigns.com

2 1

boost.lockfree update
by Tim Blechmann 31 Aug '10

31 Aug '10

hi all, i've did some updates to boost.lockfree the biggest difference to earlier snapshots is, that it includes a fixed-size single-producer/single-consumer ringbuffer. besides, the documentation is based on doxygen now. snapshots are available from [1], docs from [2] and my git repository can be found at [3] and cloned from [4]... cheers, tim [1] http://tim.klingt.org/code/projects/boost-lockfree/files [2] http://tim.klingt.org/boost_lockfree/ [3] http://tim.klingt.org/git?p=boost_lockfree.git [4] git://tim.klingt.org/boost_lockfree.git -- tim(a)klingt.org http://tim.klingt.org The first question I ask myself when something doesn't seem to be beautiful is why do I think it's not beautiful. And very shortly you discover that there is no reason. John Cage.

11 29

https://svn.boost.org/trac/boost/ticket/4515 Nasty naming conundrum? (Or does C++ need a 'not using ...; ' statement?)
by Paul A. Bristow 31 Aug '10

31 Aug '10

https://svn.boost.org/trac/boost/ticket/4515 has uncovered a nasty example of name ambiguity caused by the addition of <random> to the Standard Library. As the Standard Library expands, it may not be the last:-( http://tinyurl.com/2blmq3l gives an example of details of the ambiguity of the name 'binomial_distribution'. "error: reference to ???binomial_distribution??? is ambiguous" Random library defines 'binomial_distribution' and so 'using namespace std;' brings this name into std scope implicitly because it is a library item name (explicitly if random is included or perhaps implicitly by some '#include <std>;' declaration). But Boost.Math also defines the name 'binomial_distribution' but in the namespace boost::math. So this implies that it may be necessary to fully qualify boost::math::binomial_distribution at all uses. Ugh! We don't want to add namespace qualifiers everywhere because it messes up the simplicity of the example, but without them the code *might not* compile on C++0x compilers depending upon whether <random> happens to get included or not. To my ignorant surprise, 'using boost::math::binomial_distribution;' does not trump 'using namespace std;', despite being explicit *if it is at global scope ()*. But 'using boost::math::binomial_distribution;' works as I expected only at *local* scope. (Is this right language gurus? It feels too complicated?) Solution are: 1 Always fully qualify names like "boost:math::binomial_distribution<> my_bd;' This is hideously verbose. 2 Use " std::cout;" etc (instead of "using namespace std;" and "cout <<..." , but it gets tediously verbose. 3 Use "using std::cout;" etc instead of "using namespace std;", so we can still write cout << .. << endl; I have always favoured this solution because it documents clearly which functions are being used, and avoids the tedium of writing 'std::cout;'. (And from habit - because "using namespace std;" seemed to cause trouble using early MSVC). But it does add some clutter and *must not be done at global scope in .hpp files* - because it would quietly commit all those who #include to this definition (which may not be what they want/expect). 4 Use "using boost:math::binomial_distribution;" at local scope (but NOT at global scope). (Include files could be used to make this less verbose if there a lots of functions?) 5 Use a namespace alias for boost::math:: to reduce the verbosity of Richards proposed fix with ticket/4515. This feels like a sticking plaster solution? and is still nearly as ugly is 'bm::binomial_distribution'. Overall, John Maddock and I having pondered the least worst solution and are inclined to recommend: a Avoid using global "using namespace anything;" b For each include like <iostream>, use "using std::cout;" statements at local scope for included .hpp files, and at global (or local) scope for source .cpp files (or always write the fully qualified "std::cout << ... "). c For each boost::math include, like "#include <boost:math::binomial_distribution>", provide a "using boost:math::binomial_distribution;" statements (at local scope for included .hpp files and at global (or local) scope for source .cpp files). This may seem an obscure problem, but are there likely to be increasing number of name clashes like this as libraries increase in number? Views? Paul PS My proposal for adding a "not using ... " statement to C++ has so far got a less than warm reception ;-) Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow(a)hetp.u-net.com

2 1

[thread] Any way to avoid creating the .tls section on Windows
by Rush Manbert 31 Aug '10

31 Aug '10

Yet another bizarre question... (the easy ones have all been answered by now) This is a Windows-specific question. We build a dll that is loaded with the LoadLibrary function. Indirectly (through a third-party library), that dll links against the boost thread library. For reasons that I won't go into, the existence of the .tls section in the resulting binary is problematic for us. I looked at the code and found this comment inside the file tss_pe.cpp: //The following line has an important side effect: //if the TLS directory is not already there, it will //be created by the linker. In other words, it forces a tls //directory to be generated by the linker even when static tls //(i.e. __declspec(thread)) is not used. //The volatile should prevent the optimizer //from removing the reference. I'm not much of a Windows guy and I currently don't understand what is going on in tss_pe.cpp. I did a search of the boost sources and I don't find __declspec(thread) used anywhere, which was encouraging. I'm wondering two things: 1) Why does the code force a .tls section to be created, even when static tls is not being used? 2) If we know that static tls is not used in any of the code, is it safe to remove the .tls section from the PE file? (We know a lot about manipulating PE files, so definitely know how to do this.) We have experimented with removing the .tls section by hand and running the dll, and everything seems to work, but I'm really hoping that Anthony Williams might take pity on me and provide some information. Thanks, Rush

2 1

Re: [boost] [Boost-users] Generators and Iterators [was: Re: Overloading boost::for_each()]
by Dave Abrahams 30 Aug '10

30 Aug '10

Sent from my iPhone On Aug 30, 2010, at 3:26 PM, Mathias Gaunard <mathias.gaunard(a)ens-lyon.org> wrote: > I don't really understand your question, so I've put together a practical example, that is available on the vault: > <http://www.boostpro.com/vault/index.php?action=downloadfile&filename=genera…> And if you'd put that in a github repo I'd have been able to peruse it with my coveted but awkward mobile device ;-)

1 0