- Boost-users - lists.boost.org

[BGL] dynamic_properties for graph attributes
by Paul Hilbert 07 Jun '09

07 Jun '09

The adjacency_list class constructor takes a property type for graph attributes. However I could not figure out how to create the appropriate dynamic_property map for graph attributes and - not surprisingly - this subtle detail is left out in the "documentation". Maybe someone can enlighten my path (and those of all people I found asking the same question without getting any responses). Greetings, Paul Hilbert

2 4

[Math/Statistical Distributions] Help on using distributions' global accessors
by Marco Guazzone 07 Jun '09

07 Jun '09

Dear Boost users, I don't understand why the code in the attached file "test_distributions_ko.zip" does not work. :( It compiles without problems, but as I run it I get the following error as soon as the *variance* accessor is called: --- [error] --- Running 2 test cases... ... unknown location(0): fatal error in "exponential_distribution": memory access violation at address: 0x7fffa6254ff8: no mapping at fault address test.cpp(34): last checkpoint *** 1 failure detected in test suite "test::stats test suite" --- [/error] --- I've also tried to replace the use of inheritance with the removal of class "exponential_distribution" and directly injecting inside my namespace the Boost one, that is: namespace test { namespace stats { using ::boost::math::exponential_distribution; using ::boost::math::exponential; }} but without success. Instead, the error *disappear* if I use the code in "test_distributions_ok.zip", where instead of using inheritance and "injection" I use membeship (i.e., composition). Why? My compiler is GCC 4.3.2 and my system is Fedora 10 x86_64. If you want to try the attached code you can simply type 'make' from your shell (provided you have a unix like system) and then run the command "./test". A note about the code: you may ask yourself why I'm redefining some functions already defined by the Boost library. The reason lies in the fact that my final goal is to create a wrapping library in order to change without pain the underlying real implementation. An help or a hint would be very very very appreciated!! :) Thank you very much! -- Marco

1 1

[shared pointer] - question about different types pointing to the same object
by Robert Ramey 06 Jun '09

06 Jun '09

I've looked through the shared_ptr documentation and am still puzzled about something. suppose I have class base1 { virtual ~base1; ... }; class derived1 : public base1 { .... }; shared_ptr<derived1> pd1(new derived1) shared_ptr<base1> pb1(pd); ? do pd1 and pb1 refer to the same object? class base2 { virtual ~base2; ... }; class derived3 : public base1, public base2 { ... }; shared_ptr<base2> pb2(pd1); ? do pb1 and pb2 refer to the same object? I'm presuming they do, but it's not really clear to me that this would work. To check this I could downcast everything to derived3. BUT when I have pb1 and pb2, I don't know what to downcast to. since there could be class derived4 : public base1, public base2 { ... }; So how could I verify whether an arbitrary pb1 and pb2 point to the same object or not? Robert Ramey

3 2

[BOOST] [TEST] Dumping the memory leak into Log File
by Suraj Gupta, Gurgaon 06 Jun '09

06 Jun '09

Hi All, Memory leak information is displayed onto the console window but I want to write the memory leak information in the log file I am creating? Could you please let me know how can I achieve this? Thanks Suraj 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 HCL 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 HCL 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. Before opening any mail and attachments please check them for viruses and defect. -----------------------------------------------------------------------------------------------------------------------

3 2

Bug Sprint Report for Friday, June 5th
by Marshall Clow 06 Jun '09

06 Jun '09

The boost bug sprint started Friday, May 29th, and runs through Sunday June 7th. We've only got two more days - keep up the good work! Status <https://svn.boost.org/trac/boost/report/1> 7:00 AM PDT 5/29: 797 open tickets. 7:45 AM PDT 5/30: 772 open tickets. 6:00 AM PDT 5/31: 761 open tickets. 6:00 AM PDT 6/2: 747 open tickets. 6:00 AM PDT 6/3: 748 open tickets. 6:00 AM PDT 6/4: 739 open tickets. 8:00 AM PDT 6/5: 730 open tickets. 7:00 AM PDT 6/6: 719 open tickets. Activity: 5/29: 6 new tickets, 77 modifications, 25 tickets closed 5/30: 2 new tickets, 42 modifications, 17 tickets closed 5/31: 2 new tickets, 27 modifications, 8 tickets closed 6/1: 2 new tickets, 42 modifications, 17 tickets closed 6/2: 5 new tickets, 18 modifications, 5 tickets closed. 6/3: 4 new tickets, 19 modifications, 2 tickets closed. 6/4: 3 new tickets, 42 modifications, 24 tickets closed. 6/5: 3 new tickets, 35 modifications, 8 tickets closed. [ Numbers may not add up because I am counting via two different methods, using data that is time-stamped in two different time zones. Also, tickets can be closed and reopened. ] What can you do? See <https://svn.boost.org/trac/boost/wiki/BugSprintJune2009> for details. I've added four new reports to the trac: Open ticket count by owner: <https://svn.boost.org/trac/boost/report/18> Open ticket count by component: <https://svn.boost.org/trac/boost/report/19> Open ticket count by ticket type: <https://svn.boost.org/trac/boost/report/20> Open ticket count by milestone: <https://svn.boost.org/trac/boost/report/21> There's been a lot of discussion on the list about tickets; and there are about a dozen patches that have been tested and are ready to be applied. If you're looking to help, you can look at some of the older bugs, say, the ones for Boost 1.36, and determine if they still apply. If they do, note that in the ticket. There are 35 tickets that are still open that are marked as "to be fixed in Boost 1.36" See <https://svn.boost.org/trac/boost/report/3> for a list of open tickets by milestone. --------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do. 1) Marshall Clow (coordination, Mac OS X characterization) 2) Beman Dawes (filesystem, system, timer) 3) Doug Gregor (function, graph, logic, mpi, numeric, property_map, signals) 4) "joel falcou" <joel.falcou(a)u-psud.fr> ( linux gcc testing/VC 2008 testing, patching) 5) Michael Caisse <boost(a)objectmodelingdesigns.com> (bug fixing) 6) Jeremiah Willcock <jewillco(a)osl.iu.edu> (will test and commit graph patches) 7) David Abrahams (iterator, python) 8) Sohail Somani (patches for g++ 4.2.4) 9) Steven Watanabe <watanabesj(a)gmail.com> (bug fixes, como) 10) vicente.botet" <vicente.botet(a)wanadoo.fr> 11) Stjepan Rajko <stjepan.rajko(a)gmail.com> (fusion) 12) Daniel Wallin (parameter, ...) -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

1 0

[boost.typeof] Using boost::bind with BOOST_AUTO
by Roberto Gim�nez 06 Jun '09

06 Jun '09

I have the following code: #include <boost/typeof/typeof.hpp> #include <boost/bind.hpp> void test() { } int main(int argc, char** argv) { BOOST_AUTO(a, boost::bind(&test)); } But when I try to compile, I get errors: CC -m64 -erroff=wvarhidemem,hidevf,hidevfinvb -errtags=yes -library=stlport4 -mt -c -g -I/home/gimenero/include -o build/Debug/Sun12-Solaris-Sparc/main.o main.cc CC -m64 -erroff=wvarhidemem,hidevf,hidevfinvb -errtags=yes -library=stlport4 -mt -c -g -I/home/gimenero/include -o build/Debug/Sun12-Solaris-Sparc/main.o main.cc "main.cc", line 11: Error, nomatchoverin: Could not find a match for boost::type_of::encode<boost::type_of::V, boost::type_of::T> (boost::_bi::bind_t<void, void(*)(), boost::_bi::list0>) needed in main(int, char**). "main.cc", line 11: Error, nomatchoverin: Could not find a match for boost::type_of::encode<boost::type_of::V, boost::type_of::T> (boost::_bi::bind_t<void, void(*)(), boost::_bi::list0>) needed in main(int, char**). "main.cc", line 11: Error, nomatchoverin: Could not find a match for boost::type_of::encode<boost::type_of::V, boost::type_of::T> (boost::_bi::bind_t<void, void(*)(), boost::_bi::list0>) needed in main(int, char**). ... many times. Does BOOST_AUTO supports boost::bind?

3 7

Does Boost.Test support std::wstring log messages?
by Tan, Tom (Shanghai) 06 Jun '09

06 Jun '09

Is it possible to use Boost.Test macros with std::wstring directly like this: BOOST_TEST_MESSAGE(L"test log"); ? I tried but it does not work. I find that \test\utils\basic_cstring\basic_cstring.hpp has a templated string implementation. It seems to imply that wide char are supported by Boost.Test. Can anyone please let me know how? Thanks. tom

2 1

[Boost] [Test] [1.38] "can't use testing tools before framework is initialized"
by Greg Christopher 06 Jun '09

06 Jun '09

Hi, I am trying to integrate boost.test into an existing test program with its own framework. Therefore I'd like to use that program's main. I am currently running into this runtime error when calling BOOST_WARN_MESSAGE(1, "string"). I have tried three different things to avoid this condition: 1) I declared a TEST_SUITE using the BOOST_AUTO_TEST_SUITE() and END() macros. Probably not what I want because I want my own main to keep control, but figured it would generate a main that would allow the initialization to happen. 2) I called init_unit_test_suite( argc, argv ). Even though it was called, I am still getting this. 3) I defined a cpp_main(). This never got called. I was hoping that the existence of this symbol would cause initialization to happen elsewhere. My desired control flow is to have this test program in control and to use the BOOST logging tools. I am trying to slip in boost.test with a minimum of changes to this program. I have hooked its logging function to call boost logging facilities instead; just can't get past this problem. Thanks for any help! Greg

3 9

[mpi] could all_reduce handle MPI_IN_PLACE ?
by Alain Miniussi 05 Jun '09

05 Jun '09

Hi, There doesn't seems to be an elgant way to do an in place all_reduce on array right now (Although I only stumbled on the issue after I moved to openmpi 1.3.2). That is, if all_reduce_impl is called with (in_values == out_values) MPI is allowed to compain with a MPI_ERR_BUF. Of course, one can call all_reduce with static_cast<T*>(MPI_IN_PLACE) but I do not find that solution very elegant. Would it be a problem to modify all_reduce_impl into: template<typename T, typename Op> void all_reduce_impl(const communicator& comm, const T* in_values, int n, T* out_values, Op /*op*/, mpl::true_ /*is_mpi_op*/, mpl::true_ /*is_mpi_datatype*/) { if (in_values == out_values) { in_values = static_cast<T*>(MPI_IN_PLACE); } BOOST_MPI_CHECK_RESULT(MPI_Allreduce, (const_cast<T*>(in_values), out_values, n, boost::mpi::get_mpi_datatype<T>(*in_values), (is_mpi_op<Op, T>::op()), comm)); } It worked for me, and if there is an agreement I can propose a patch. Regards, -- Alain Miniussi http://www.oca.eu/alainm Equipe CRIMSON https://crimson.oca.eu +33 492 00 30 09

1 0

[proto] declaring result type for callable contexts
by Maurizio Vitale 05 Jun '09

05 Jun '09

Eric, It seems like result types must be defined inside a struct eval, but examples in the documentation show the form commented out below. Is this a recent change? Also, in absence of a result_type declaration inside struct eval {...} the type defaults to int. Would it be possible to make it void or some_ugly_looking_type_that_tell_me_i_is_all_wrong? int might happen to be what the user wants, until he decide to change it and hides the problem. template<typename Expr> struct my_context : proto::callable_context<const my_context<Expr> > { struct eval {typedef double result_type;}; // doesn't work (anymore?) //typedef double result_type; };

3 5