August 2006 - Boost - lists.boost.org

Re: [boost] Numerical integration library?
by Sohail Somani 01 Aug '06

01 Aug '06

> -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of John Maddock > Sent: Tuesday, August 01, 2006 9:25 AM > To: boost(a)lists.boost.org > Subject: Re: [boost] Numerical integration library? > > Sohail Somani wrote: > > I wouldn't doubt that at all. People look at me funny when I mention > > "root finding". > > > > Or maybe theyre just looking at me funny? :) > > Not at all, I take it you mean root finding as in: > > http://freespace.virgin.net/boost.regex/toolkit/libs/math/doc/ > html/math_toolkit/toolkit.html#math_toolkit.toolkit.root_findi > ng_with_derivatives > > or > > http://freespace.virgin.net/boost.regex/toolkit/libs/math/doc/ > html/math_toolkit/toolkit.html#math_toolkit.toolkit.root_findi > ng_without_derivatives > > ? Yes this is what I meant. It seems that there is different nomenclature regarding this relatively common concept. Is that your library you pointed to above? Sohail

2 1

Re: [boost] Numerical integration library?
by Sohail Somani 01 Aug '06

01 Aug '06

> -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of Frederick Akalin > Sent: Monday, July 31, 2006 8:38 PM > To: boost(a)lists.boost.org > Subject: Re: [boost] Numerical integration library? > > "Numerical integration" is often loosely used to mean > quadrature, ODE > solving, and PDE solving. I was just following the terminology on > the Wiki; I'm sorry if I wasn't clear. I wouldn't doubt that at all. People look at me funny when I mention "root finding". Or maybe theyre just looking at me funny? :)

2 1

Boost regression notification (2006-08-01 [RC_1_34_0])
by Douglas Gregor 01 Aug '06

01 Aug '06

Boost Regression test failures Report time: 2006-08-01T07:11:38Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/i… 271 failures in 23 libraries algorithm/string (1) concept_check (1) filesystem (4) graph (5) io (1) iostreams (11) mpl (6) numeric/conversion (4) numeric/interval (1) numeric/ublas (7) parameter (22) program_options (9) python (85) random (1) rational (4) regex (4) serialization (25) signals (16) spirit (1) test (2) tr1 (51) typeof (9) utility (1) |algorithm/string| regex: borland-5_6_4 |concept_check| class_concept_check_test: vc-7_1-stlport |filesystem| mbcopy: sun-5.8 operations_test: vc-7_1-stlport operations_test_dll: vc-7_1-stlport wide_test: sun-5.8 |graph| adjacency_matrix_test: vc-7_0 csr_graph_test: sun-5.8 graphviz_test: msvc-8.0 msvc-8.0 vc-7_1-stlport |io| ios_state_unit_test: gcc-4.1.0_linux_x86_64 |iostreams| bzip2_test: msvc-7.1 msvc-8.0 compose_test: borland-5_6_4 example_test: vc-6_5-stlport filtering_stream_test: msvc-8.0 vc-7_1-stlport finite_state_filter_test: cw-9.4 gzip_test: msvc-7.1 msvc-8.0 zlib_test: msvc-7.1 msvc-8.0 |mpl| multiset: gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.0_linux_x86_64 gcc-4.1.1_sunos_i86pc gcc-4_0_3_tru64 vector_c: sun-5.8 |numeric/conversion| converter_test: borland-5_8_2 traits_test: borland-5_8_2 udt_example_0: borland-5_8_2 udt_support_test: borland-5_8_2 |numeric/interval| test_float: vc-7_1-stlport |numeric/ublas| concepts: vc-7_1-stlport vc-7_1-stlport test1: vc-7_1-stlport test2: vc-7_1-stlport test4: vc-7_1-stlport test5: vc-7_1-stlport vc-7_1-stlport |parameter| basics: borland-5_6_4 borland-5_8_2 duplicates: borland-5_6_4 borland-5_8_2 maybe: vc-6_5 vc-6_5-stlport vc-7_0 preprocessor: borland-5_6_4 borland-5_8_2 sun-5.8 vc-6_5 vc-6_5-stlport python-parameter-test: vc-6_5 vc-6_5-stlport vc-7_0 sfinae: borland-5_8_2 vc-6_5-stlport singular: borland-5_6_4 borland-5_8_2 unnamed_fail: vc-6_5 vc-6_5-stlport vc-7_0 |program_options| cmdline_test_dll: cw-9.4 options_description_test_dll: cw-9.4 parsers_test_dll: cw-9.4 positional_options_test_dll: cw-9.4 unicode_test_dll: borland-5_8_2 cw-9.4 variable_map_test_dll: borland-5_8_2 cw-9.4 winmain_dll: cw-9.4 |python| andreas_beyer: sun-5.8 args: sun-5.8 auto_ptr: sun-5.8 back_reference: sun-5.8 bases: gcc-3_4_4_tru64 gcc-4_0_3_tru64 sun-5.8 ben_scott1: sun-5.8 bienstman1: sun-5.8 bienstman2: sun-5.8 bienstman3: sun-5.8 borrowed: sun-5.8 callbacks: sun-5.8 const_argument: sun-5.8 crossmod_exception: sun-5.8 data_members: sun-5.8 defaults: sun-5.8 dict: sun-5.8 docstring: sun-5.8 enum: sun-5.8 exception_translator: sun-5.8 exec: cw-9.4 darwin-4.0.1 gcc-3_4_4_tru64 gcc-4_0_3_tru64 msvc-8.0 qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp sun-5.8 extract: sun-5.8 implicit: sun-5.8 indirect_traits_test: sun-5.8 injected: sun-5.8 iterator: sun-5.8 keywords: sun-5.8 list: sun-5.8 long: sun-5.8 minimal: sun-5.8 multi_arg_constructor: sun-5.8 nested: sun-5.8 numpy: sun-5.8 object: sun-5.8 object_manager: sun-5.8 opaque: sun-5.8 operators: sun-5.8 pearu1: sun-5.8 pickle1: sun-5.8 pickle2: sun-5.8 pickle3: sun-5.8 pickle4: sun-5.8 pointee: gcc-3_4_4_tru64 gcc-4_0_3_tru64 sun-5.8 pointer_type_id_test: gcc-3_4_4_tru64 gcc-4_0_3_tru64 sun-5.8 pointer_vector: sun-5.8 polymorphism: sun-5.8 polymorphism2: sun-5.8 polymorphism2_auto_ptr: sun-5.8 properties: sun-5.8 raw_ctor: sun-5.8 return_arg: sun-5.8 select_arg_to_python_test: sun-5.8 select_from_python_test: darwin-4.0.1 sun-5.8 select_holder: sun-5.8 shared_ptr: sun-5.8 slice: sun-5.8 staticmethod: sun-5.8 stl_iterator: sun-5.8 str: sun-5.8 string_literal: sun-5.8 test_pointer_adoption: sun-5.8 try: sun-5.8 tuple: sun-5.8 upcast: gcc-3_4_4_tru64 gcc-4_0_3_tru64 sun-5.8 vector_indexing_suite: sun-5.8 virtual_functions: sun-5.8 voidptr: sun-5.8 wrapper_held_type: sun-5.8 |random| random_test: intel-linux-9.0 |rational| rational_test: borland-5_6_4 vc-6_5 vc-6_5-stlport vc-7_0 |regex| object_cache_test: gcc-3.3.6 gcc-3.4.4 gcc-4.1.1_sunos_i86pc regex_regress_threaded: gcc-4_0_3_tru64 |serialization| test_class_info_load_text_warchive: vc-6_5 test_non_default_ctor2_text_archive: qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp test_non_default_ctor2_text_archive_dll: qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp test_non_default_ctor2_text_warchive: qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp test_non_default_ctor2_text_warchive_dll: qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp test_reset_object_address: vc-7_0 test_reset_object_address_dll: vc-7_0 test_set_text_archive_dll: msvc-8.0 test_simple_class_binary_archive_dll: vc-6_5 test_simple_class_text_archive_dll: vc-6_5 test_simple_class_text_warchive_dll: vc-6_5 test_simple_class_xml_archive_dll: vc-6_5 test_simple_class_xml_warchive_dll: vc-6_5 test_variant_xml_archive: borland-5_8_2 test_variant_xml_archive_dll: borland-5_8_2 test_variant_xml_warchive: borland-5_8_2 test_variant_xml_warchive_dll: borland-5_8_2 |signals| dead_slot_test: gcc-3.3.6 gcc-3.3.6_linux qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp qcc-3.3.5_gpp trackable_test: gcc-3.3.6 gcc-3.3.6_linux qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp qcc-3.3.5_gpp |spirit| mix_and_match_trees: sun-5.8 |test| parameterized_test_test: vc-6_5 vc-6_5-stlport |tr1| run_random: sun-5.8 std_run_complex_overloads: sun-5.8 std_run_random: sun-5.8 std_test_bind: sun-5.8 std_test_complex: sun-5.8 std_test_function: sun-5.8 std_test_hash: sun-5.8 std_test_mem_fn: sun-5.8 std_test_random: sun-5.8 std_test_reference_wrapper: sun-5.8 std_test_reference_wrapper_tricky: gcc-3.2.3_linux gcc-3.3.6_linux gcc-3.4.5_linux gcc-3.4.5_linux_x86_64 gcc-4.0.3_linux gcc-4.1.0_linux_x86_64 intel-linux-9.0 mingw-3_4_2 msvc-7.1 msvc-8.0 qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp vc-7_1-stlport std_test_result_of: sun-5.8 std_test_shared_ptr: sun-5.8 std_test_tuple: sun-5.8 std_test_tuple_tricky: sun-5.8 std_test_type_traits: sun-5.8 test_boost: vc-7_1-stlport test_hash: vc-7_1-stlport test_random: sun-5.8 vc-7_1-stlport test_reference_wrapper_tricky: gcc-3.2.3_linux gcc-3.3.6_linux gcc-3.4.5_linux gcc-3.4.5_linux_x86_64 gcc-4.0.3_linux gcc-4.1.0_linux_x86_64 intel-linux-9.0 mingw-3_4_2 msvc-7.1 msvc-8.0 qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp test_regex: vc-7_1-stlport test_type_traits: sun-5.8 tr1_tky_function_type_test: sun-5.8 |typeof| function_binding_emulation: sun-5.8 function_binding_native: vc-6_5 vc-6_5-stlport vc-7_0 nested_typedef_emulation: cw-9.4 odr_no_uns: vc-6_5 vc-6_5-stlport vc-7_0 template_tpl_emulation: sun-5.8 |utility| operators_test: gcc-3.4.5_linux_x86_64

1 0

Re: [boost] [serialization] MSVC8 runtime check error
by brass goowy 01 Aug '06

01 Aug '06

John Reid wrote: > > I'm getting a runtime check error from MSVC8 in the following code > checked out from cvs_head: > > serialization/collections_load_imp.hpp > line 116 > > ... > > template<class Archive, class Container, class InputFunction, class R> > inline void load_collection(Archive & ar, Container &s) > { > s.clear(); > // retrieve number of elements > unsigned int count; > unsigned int item_version; > ar >> BOOST_SERIALIZATION_NVP(count); > if(3 < ar.get_library_version()){ > ar >> BOOST_SERIALIZATION_NVP(item_version); > } > R rx; > rx(s, count); > InputFunction ifunc; > while(count-- > 0){ > ifunc(ar, s, item_version); > } > } > I think this function would be more flexible if the clear call was removed. Users could decide if they want to call clear() or not. If you want append-like behaviour you wouldn't call clear(). If you know the container is already empty you also wouldn't have to call clear(). Regards, Brian Wood www.webEbenezer.net

2 1

library for type erasure
by Steven Watanabe 01 Aug '06

01 Aug '06

AMDG Is there any interest in a library for type erasure? My basic idea is to define each operation separately and use a sequence of them. As a simple example: void f() { erasure<boost::mpl::vector<ostreamable, incrementable> > object(0); ++object; std::cout << object; //prints 1 } In Christ, Steven Watanabe

3 2

Re: [boost] [statistics] design/interface reprise
by John Maddock 01 Aug '06

01 Aug '06

Daniel Egloff wrote: > thanks for the proposal. > > It looks good. However I do not like the notation such as > > cdf_c(dist, x); > > for the complemented functions too much. The "_c" is not very visible. > What's about > > complemented(cdf)(dist, x); > cdf(complemented)(dist, x); > cdf<complemented>(dist, x); > > > Similarly for all other functions which have complemented versions. By > the way, complemented only makes sense for 1 dimensional > distributions. Did you think about multivariate distributions? There, > the "tail" is the complement of a ball or an ellipsoid. But this > becomes highly challenging already for moderate dimensions. > > I think the syntax for all 3 variations should be doable. My > preferences are 2 or 3. > > What do you think? Of those I would prefer (2), or else: // complemented cdf: cdf(complemented(dist, x)); // quantile from complement of probabilty: quantile(complemented(dist, q)); // estimate degrees of freedom from t // and complement of probablity: students_t::estimate_degree_of_freedom( complemented(t, q)); I'm also tempted to suggest that "complemented" is spelled "complement". I'd be interested to know what other think though. As for the multivariate case, no we haven't thought about it (there's more than enough to do at present in the univariate case), I suspect we would have to fall back on "not all operations are supported on all distributions", which would be not unreasonable in that case. A compiler error in other words. John.

2 1

[boostbook] Extra space after void parameter declaration
by Julio M. Merino Vidal 01 Aug '06

01 Aug '06

Hi, I usually write function declarations that do not take any parameters using the "old" C style; that is: int foo(void); I've now started documenting my code using Doxygen and integrating the resulting documentation into a Quickbook document. The class summary is correctly formatted because it does not include the parameter names, but the function prototypes in their description show: int foo(void ); Note the extra space after void. It looks ugly and I believe it should not be there. The attached patch seems to fix this issue. Can it be integrated? Thanks, -- Julio M. Merino Vidal <jmmv84(a)gmail.com> The Julipedia - http://julipedia.blogspot.com/

2 1

Where to place tests for BOOST_WORKAROUND?
by Gennaro Prota 01 Aug '06

01 Aug '06

Hi guys, despite proceeding on it by fits and starts I've completed the work on the new compiler identification macros. Since Rene asked for them to be committed after the 1.34 release they are still on hold (/auto-censorship here/) however I'd like to add tests for the new BOOST_WORKAROUND macro. The question is: it was, and is, a sort of private tool for boost developers, as its placement in the detail/ subdirectory emphasizes, so we probably (uncertainty and doubt) don't want its test results to show in the regression reports. If so, where should those tests go? -- [ Gennaro Prota, C++ developer for hire ]

2 2

Boost regression testing status
by Gennaro Prota 01 Aug '06

01 Aug '06

Hi, I'd like to point your attention toward the current status of our regression testing. I'll not express opinions, but these are some facts about 1.34: - Huang-WinXP-x64 - graph - graphviz_test / msvc-8.0 LINK : fatal error LNK1181: cannot open input file '[...]\bgl-viz-vc80-gd-1_34.lib' - For some failures no error message is reported, so that it is pretty much impossible for the developer to fix them; e.g.: http://tinyurl.com/zmpwk - metacomm-v2 - algorithm/minmax - minmax / msvc-7.0 'vsvars32.bat' is not recognized as an internal or external command... - OSL4-V2 - python - andreas_beyer / sun-5.8 #error Python 2.2 or higher is required for this version of Boost.Python. - RudbekAssociates-V2 - iostreams - bzip2_test / msvc-7.1 LINK : fatal error LNK1181: cannot open input file '[...]\boost_iostreams-vc71-gd-1_34.lib' The list is not exhaustive. -- [ Gennaro Prota, C++ developer for hire ]

5 20

Re: [boost] Numerical integration library?
by Sohail Somani 01 Aug '06

01 Aug '06

> -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of Frederick Akalin > Sent: Monday, July 31, 2006 1:17 AM > To: boost(a)lists.boost.org > Subject: [boost] Numerical integration library? > > I notice numerical integration was one of the items listed in the > ExpandedMathematicsLibrary entry under WantedLibraries in the > Wiki. Has > anyone done any work on this? I've been looking into this > problem space > lately; I had the germ of an idea that, with the magic of templates, > most ODE solvers (e.g. Euler, Runge-Kutta, etc.) could be > written in a > container-agnostic format and in a form closely resembling that which > you would find in a textbook. (I can post some > proof-of-concept code if > this isn't clear.) I've looked around and haven't seen > anything similar, > but I'm no expert on scientific programming. I'm unsure what ODE's have to do with integrals. Anyway, for solving PDEs one should look at http://www10.informatik.uni-erlangen.de/~pflaum/expde/public_html/index. html for an example. I'd be interested to know if anyone has used this library :) Sohail

2 1