- Boost - lists.boost.org

Re: [boost] VC8 function template ambiguity problems
by Michael Stevens 30 Jun '05

30 Jun '05

On Wednesday 29 June 2005 19:40, "Peter Dimov" <pdimov(a)gmail.com> wrote: > Michael Stevens wrote: > > template<class V> > > void hard (V &data, const typename vector_range<V>::range_type &r) > > {} > > template<class V> > > void hard (vector_slice<V> &data, const typename > > vector_slice<V>::range_type &r) > > {} > > [...] > > > It thinks the functions 'hard' are ambiguous despite the fact that > > the first parameter is more specialised in the second version. > > The functions do seem ambiguous to me. I see no partial ordering between > them. I'm being a little hard on the compiler here. In the single parameter case. Things are easy, the second template is more specialised. The difficultly is the second parameter. In the first case we have vector_range<V>::range_type in the second vector_slice<V>::range_type The crux of the problem is these two are actually the same type! I think VC is missing this when it performs 'argument deduction against the other function template' to determine if the templates are 'at least as specialized'. See 14.5.5.2 para 4. At least some other modern compilers (GCC4.0, Intel 8.0 CW-9.4) are with on this on this! VC has no problems if we help it by using 'vector_range<V>::range_type' in both cases. Thanks, Michael

1 0

Re: [boost] VC8 function template ambiguity problems
by Michael Stevens 30 Jun '05

30 Jun '05

On Wednesday 29 June 2005 09:34,Rob Stewart <stewart(a)sig.com> wrote: > What about putting them in a class template? Then you could > introduce typedefs to simplify the expressions the compiler must > grok. Rob, thanks for the reply. It stimulated a few ideas and I now have a solution. The actual problem (in uBLAS) was slightly more complex then the 'hard' function as the return value depended also on the template argument. With a few helper classes and a lot a PTS I can deduce the return value and provide apply functions. Now VC only has order overloaded template functions with single arguments and is happy. Thanks, Michael

1 0

[BGL] Help! read_graphviz has syntax error
by Tan Kwee Heong 30 Jun '05

30 Jun '05

Hi, I posted this on the Boost User's group and did not have any response. I'll try again on the Boost Developers' group. On Win2K ( using cygwin g++ 3.3.1 ) using boost_1_32_0, read_graphviz has a syntax error when reading a digraph .dot file. The simplest way to reproduce this is to build a static libbgl-viz.lib and run the libs/graph/example/graphviz on the graphviz_test.dot input data. Note that the bjam reports that the testcase pass, but if you execute the graphviz.exe binary manually, you'll see the syntax error, like so: | > gcc/graphviz ../../../../../../../../../libs/graph/example/graphviz_test.dot | ... | syntax error | The same sources, when built with VC7.1 will pass with the correct output, when run manually. Like so : | > vc7/graphviz ../../../../../../../../../libs/graph/example/graphviz_test.dot | ... | a1 --> a2 b3 | a2 --> a3 | a3 --> end | a0 --> a1 a2 a3 | ... I can provide more information if needed. The basic question I have is whether this is a known problem for g++ 3.3.1 or a simple bug that someone more knowledgeable can take a look/fix. Thanks,

1 0

Re: [boost] Library Proposal: Boost.Geom 2D and3DGeometricPrimitives
by Hickerson, David A 29 Jun '05

29 Jun '05

I will see about putting it on the Boost SandBox. If what I have would help with this effort, I'd be glad to help. Dave -----Original Message----- From: Andy Little [mailto:andy@servocomm.freeserve.co.uk] Sent: Wednesday, June 29, 2005 2:35 AM To: boost(a)lists.boost.org Subject: Re: [boost] Library Proposal: Boost.Geom 2D and3DGeometricPrimitives "Hickerson, David A" wrote [..] > I have done some of this in the library I wrote in 97. Is that available to see? Andy Little _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Boost regression notification (2005-06-29)
by Douglas Gregor 29 Jun '05

29 Jun '05

Boost regression test failures ------------------------------ Report time: 2005-06-29T15:42:30Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. random preprocessor io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 290 failures in 12 libraries: io (1) numeric/conversion (3) numeric/ublas (21) preprocessor (1) program_options (12) python (4) random (2) serialization (230) spirit (5) test (6) thread (1) wave (4) |io| ios_state_unit_test: intel-win32-8_1 |numeric/conversion| udt_example_0: borland-5_6_4 msvc vc-6_5 |numeric/ublas| concepts: cw-9_4 cw-9_4 cw-9_5-darwin test1: cw-9_4 cw-9_4 cw-9_5-darwin test2: cw-9_4 cw-9_4 cw-9_5-darwin test3: cw-9_4 cw-9_4 cw-9_5-darwin test4: cw-9_4 cw-9_4 cw-9_5-darwin test5: cw-9_4 cw-9_4 cw-9_5-darwin test6: cw-9_4 cw-9_4 cw-9_5-darwin |preprocessor| seq: cw-8_3 |program_options| cmdline_test: vc-7_0 cmdline_test_dll: mingw-3_4_2 vc-7_0 parsers_test: vc-7_0 parsers_test_dll: vc-7_0 positional_options_test_dll: mingw-3_4_2 unicode_test: vc-7_0 unicode_test_dll: cw-9_5-darwin gcc-3_3-darwin vc-7_0 variable_map_test: vc-7_0 variable_map_test_dll: vc-7_0 |python| extract: gcc-3.3.6-linux list: gcc-3.3.6-linux operators: gcc-3.3.6-linux slice: gcc-3.3.6-linux |random| random_test: intel-win32-8_1 intel-win32-8_1 |serialization| test_array_text_archive_dll: cw-9_5-darwin test_array_text_warchive_dll: cw-9_5-darwin test_array_xml_archive_dll: cw-9_5-darwin test_array_xml_warchive_dll: cw-9_5-darwin test_binary_text_archive_dll: cw-9_5-darwin test_binary_text_warchive_dll: cw-9_5-darwin test_binary_xml_archive_dll: cw-9_5-darwin test_binary_xml_warchive_dll: cw-9_5-darwin test_class_info_load_binary_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_binary_archive_dll: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_archive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_archive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_warchive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_warchive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux vc-6_5 test_class_info_load_xml_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_archive_dll: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_warchive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_warchive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_save_text_archive_dll: cw-9_5-darwin test_class_info_save_text_warchive_dll: cw-9_5-darwin test_class_info_save_xml_warchive_dll: cw-9_5-darwin test_const_load_fail1: borland-5_6_4 test_const_load_fail1_nvp: borland-5_6_4 test_const_load_fail2: borland-5_6_4 test_const_load_fail2_nvp: borland-5_6_4 test_const_save_fail1: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_const_save_fail2: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_const_save_fail3: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_contained_class_text_archive_dll: cw-9_5-darwin test_contained_class_text_warchive_dll: cw-9_5-darwin test_contained_class_xml_archive_dll: cw-9_5-darwin test_contained_class_xml_warchive_dll: cw-9_5-darwin test_cyclic_ptrs_text_archive_dll: cw-9_5-darwin test_cyclic_ptrs_text_warchive_dll: cw-9_5-darwin test_cyclic_ptrs_xml_archive_dll: cw-9_5-darwin test_cyclic_ptrs_xml_warchive_dll: cw-9_5-darwin test_delete_pointer_text_archive_dll: cw-9_5-darwin test_delete_pointer_text_warchive_dll: cw-9_5-darwin test_delete_pointer_xml_archive_dll: cw-9_5-darwin test_delete_pointer_xml_warchive_dll: cw-9_5-darwin test_demo_auto_ptr_dll: cw-9_5-darwin test_demo_dll: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_exception_dll: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_fast_archive_dll: msvc vc-6_5 test_demo_pimpl_dll: cw-9_5-darwin msvc vc-6_5 vc-7_0 test_demo_polymorphic_dll: cw-9_5-darwin test_demo_portable_archive: intel-win32-8_1 intel-win32-8_1 vc-7_0 vc-7_1 vc-8_0 test_demo_portable_archive_dll: intel-win32-8_1 intel-win32-8_1 test_demo_shared_ptr: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_shared_ptr_dll: cw-9_4 cw-9_4 cw-9_5-darwin msvc vc-6_5 vc-7_0 test_deque_text_archive_dll: cw-9_5-darwin test_deque_text_warchive_dll: cw-9_5-darwin test_deque_xml_archive_dll: cw-9_5-darwin test_deque_xml_warchive_dll: cw-9_5-darwin test_derived_class_ptr_text_archive_dll: cw-9_5-darwin test_derived_class_ptr_text_warchive_dll: cw-9_5-darwin test_derived_class_ptr_xml_archive_dll: cw-9_5-darwin test_derived_class_ptr_xml_warchive_dll: cw-9_5-darwin test_derived_class_text_archive_dll: cw-9_5-darwin test_derived_class_text_warchive_dll: cw-9_5-darwin test_derived_class_xml_archive_dll: cw-9_5-darwin test_derived_class_xml_warchive_dll: cw-9_5-darwin test_derived_text_archive_dll: cw-9_5-darwin test_derived_text_warchive_dll: cw-9_5-darwin test_derived_xml_warchive_dll: cw-9_5-darwin test_diamond_binary_archive: cw-8_3 cw-9_5-darwin test_diamond_binary_archive_dll: cw-9_5-darwin test_diamond_text_archive: cw-8_3 cw-9_5-darwin test_diamond_text_archive_dll: cw-9_5-darwin test_diamond_text_warchive: cw-8_3 cw-9_5-darwin test_diamond_text_warchive_dll: cw-9_5-darwin test_diamond_xml_archive: cw-8_3 cw-9_5-darwin test_diamond_xml_archive_dll: cw-9_5-darwin test_diamond_xml_warchive: cw-8_3 cw-9_5-darwin test_diamond_xml_warchive_dll: cw-9_5-darwin test_list_ptrs_text_archive_dll: cw-9_5-darwin test_list_ptrs_text_warchive_dll: cw-9_5-darwin test_list_ptrs_xml_archive_dll: cw-9_5-darwin test_list_ptrs_xml_warchive_dll: cw-9_5-darwin test_list_text_archive_dll: cw-9_5-darwin test_list_text_warchive_dll: cw-9_5-darwin test_list_xml_archive_dll: cw-9_5-darwin test_list_xml_warchive_dll: cw-9_5-darwin test_map_binary_archive_dll: msvc vc-6_5 vc-7_0 test_map_text_archive_dll: cw-9_5-darwin msvc vc-6_5 vc-7_0 test_map_text_warchive_dll: cw-9_5-darwin msvc vc-6_5 vc-7_0 test_map_xml_archive_dll: cw-9_5-darwin test_map_xml_warchive_dll: cw-9_5-darwin test_mult_archive_types: cw-9_4 cw-9_4 cw-9_5-darwin test_mult_archive_types_dll: cw-9_4 cw-9_4 cw-9_5-darwin msvc vc-6_5 test_multiple_ptrs_text_archive_dll: cw-9_5-darwin test_multiple_ptrs_text_warchive_dll: cw-9_5-darwin test_multiple_ptrs_xml_archive_dll: cw-9_5-darwin test_multiple_ptrs_xml_warchive_dll: cw-9_5-darwin test_no_rtti_binary_archive: intel-win32-8_1 test_non_default_ctor_text_archive_dll: cw-9_5-darwin test_non_default_ctor_text_warchive_dll: cw-9_5-darwin test_non_default_ctor_xml_archive_dll: cw-9_5-darwin test_non_default_ctor_xml_warchive_dll: cw-9_5-darwin test_non_intrusive_text_archive_dll: cw-9_5-darwin test_non_intrusive_text_warchive_dll: cw-9_5-darwin test_non_intrusive_xml_archive_dll: cw-9_5-darwin test_non_intrusive_xml_warchive_dll: cw-9_5-darwin test_null_ptr_text_archive_dll: cw-9_5-darwin test_null_ptr_text_warchive_dll: cw-9_5-darwin test_null_ptr_xml_warchive_dll: cw-9_5-darwin test_nvp_text_archive_dll: cw-9_5-darwin test_nvp_text_warchive_dll: cw-9_5-darwin test_nvp_xml_archive_dll: cw-9_5-darwin test_nvp_xml_warchive_dll: cw-9_5-darwin test_object_text_warchive_dll: cw-9_5-darwin test_object_xml_warchive_dll: cw-9_5-darwin test_optional_text_archive_dll: cw-9_5-darwin test_optional_text_warchive_dll: cw-9_5-darwin test_optional_xml_archive_dll: cw-9_5-darwin test_optional_xml_warchive_dll: cw-9_5-darwin test_polymorphic_text_archive_dll: cw-9_5-darwin test_polymorphic_text_warchive_dll: cw-9_5-darwin test_polymorphic_xml_archive_dll: cw-9_5-darwin test_polymorphic_xml_warchive_dll: cw-9_5-darwin test_primitive_text_warchive_dll: cw-9_5-darwin test_primitive_xml_warchive_dll: cw-9_5-darwin test_private_ctor_dll: cw-9_5-darwin test_recursion_text_archive_dll: cw-9_5-darwin test_recursion_text_warchive_dll: cw-9_5-darwin test_recursion_xml_archive_dll: cw-9_5-darwin test_recursion_xml_warchive_dll: cw-9_5-darwin test_reset_object_address_dll: cw-9_5-darwin test_set_text_archive_dll: cw-9_5-darwin test_set_text_warchive_dll: cw-9_5-darwin test_set_xml_archive_dll: cw-9_5-darwin test_set_xml_warchive_dll: cw-9_5-darwin test_shared_ptr_132_binary_archive: borland-5_6_4 test_shared_ptr_132_binary_archive_dll: borland-5_6_4 test_shared_ptr_132_text_archive: borland-5_6_4 intel-win32-8_1 test_shared_ptr_132_text_archive_dll: borland-5_6_4 test_shared_ptr_132_text_warchive: borland-5_6_4 test_shared_ptr_132_text_warchive_dll: borland-5_6_4 test_shared_ptr_132_xml_archive: borland-5_6_4 test_shared_ptr_132_xml_archive_dll: borland-5_6_4 test_shared_ptr_132_xml_warchive: borland-5_6_4 test_shared_ptr_132_xml_warchive_dll: borland-5_6_4 test_simple_class_ptr_text_archive_dll: cw-9_5-darwin test_simple_class_ptr_text_warchive_dll: cw-9_5-darwin test_simple_class_ptr_xml_archive_dll: cw-9_5-darwin test_simple_class_ptr_xml_warchive_dll: cw-9_5-darwin test_simple_class_text_archive_dll: cw-9_5-darwin test_simple_class_text_warchive_dll: cw-9_5-darwin test_simple_class_xml_archive_dll: cw-9_5-darwin test_simple_class_xml_warchive_dll: cw-9_5-darwin test_split_text_archive_dll: cw-9_5-darwin test_split_text_warchive_dll: cw-9_5-darwin test_split_xml_warchive_dll: cw-9_5-darwin test_tracking_text_archive_dll: cw-9_5-darwin test_tracking_text_warchive_dll: cw-9_5-darwin test_tracking_xml_warchive_dll: cw-9_5-darwin test_variant_text_archive_dll: cw-9_5-darwin test_variant_text_warchive_dll: cw-9_5-darwin test_variant_xml_archive_dll: cw-9_5-darwin test_variant_xml_warchive_dll: cw-9_5-darwin test_vector_text_archive_dll: cw-9_5-darwin test_vector_text_warchive_dll: cw-9_5-darwin test_vector_xml_archive_dll: cw-9_5-darwin test_vector_xml_warchive_dll: cw-9_5-darwin |spirit| bug_fixes: cw-9_5-darwin bug_fixes_debug: cw-9_5-darwin numerics_tests: gcc-3.2.3-linux numerics_tests_debug: gcc-3.2.3-linux owi_mt_tests: gcc-3_3-darwin |test| errors_handling_test: cw-9_5-darwin vc-8_0 test_fp_comparisons: borland-5_6_4 test_tools_test: cw-9_4 cw-9_4 cw-9_5-darwin |thread| test_read_write_mutex: borland-5_6_4 |wave| testwave: cw-8_3 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux

1 0

[date-time] bug determining system time
by Harald Haspl 29 Jun '05

29 Jun '05

Hello, we just found an error inside the date-time library. I use "boost::posix_time::microsec_clock::local_time()" to get the actual time. When the microseconds overflow and a new second starts, the seconds don't get incremented atomically together with the microseconds. Is this a known bug? My System: boost version 1.31.0 Linux 2.6.3, SMP (Red Hat Enterprise) 2x Intel Xeon HT Some values of consecutive calls: call: 2005-Jun-28 15:00:24.978706 call: 2005-Jun-28 15:00:24.989132 FAILURE: 2005-Jun-28 15:00:24.000105 FAILURE: 2005-Jun-28 15:00:24.000210 FAILURE: 2005-Jun-28 15:00:24.000283 FAILURE: 2005-Jun-28 15:00:24.000353 FAILURE: 2005-Jun-28 15:00:24.000424 call: 2005-Jun-28 15:00:25.000503 call: 2005-Jun-28 15:00:25.010122 call: 2005-Jun-28 15:00:25.020088 call: 2005-Jun-28 15:00:25.030194 Regards, Harald -- Harald Haspl apus | Software GmbH Bahnhofstrasse 1, A-8074 Graz-Raaba T | +43 316 401629 0 F | +43 316 401629 9 http://www.apus.co.at harald.haspl(a)apus.co.at

2 1

[serialization] ADL problem
by Vladimir Prus 29 Jun '05

29 Jun '05

With unmodified CVS state of serialization, I get errors from compiler because archive/detail/iserializer.hpp contains unqualified call to 'load', and it find both serialization's 'load', and some other 'load' that I happen to have. I wonder if ADL is desired here? IIUC, the only customization point is the 'serialize' function -- that will call user provided 'load' and 'save' explictly. So, there's no need for ADL in iserializer.hpp. With the attached patch, things start to work for me. Is it possible to apply it? - Volodya

3 16

[typeof] enums are not integral types
by Alexander Nasonov 29 Jun '05

29 Jun '05

The following sentence in typeof.htm: Other integral types, such as enums, need to be described explicitly with the BOOST_TYPEOF_INTEGRAL macro, like (BOOST_TYPEOF_INTEGRAL(MyEnum)) contrudicts with footnote in 3.9.1/7: 43) Therefore, enumerations (7.2) are not integral: however, enumerations can be promoted to int, unsigned int, long or unsigned long, as specified in 4.5 It should be easy to fix documentation. Not sure what to do with BOOST_TYPEOF_INTEGRAL, though. BTW, it reminds me of mpl::integral_c and this item in MPL TODO list: * vector_c, range_c et al. don't work with enumeration types * http://thread.gmane.org/gmane.comp.lib.boost.devel/116955 * http://article.gmane.org/gmane.comp.lib.boost.devel/116940 * http://thread.gmane.org/gmane.comp.lib.boost.user/9219 -- Alexander Nasonov

3 5

VC8 function template ambiguity problems
by Michael Stevens 29 Jun '05

29 Jun '05

Dear All, I was hoping that VC8 would finally fix up problems with it's ambiguity resolution system for function template arguments. Sadly the current beta version as used for Boost regression tests still has problems. See http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/output… for a failure in Boost::uBLAS. The same problem is not shown for previous VC compilers as the offending tests are simply disabled. The problem can easily be exemplified with the follow code which still fails on VC-8 struct range { }; template<class V> struct vector_range { typedef range range_type; }; template<class V> struct vector_slice { typedef range range_type; }; template<class V> void simple (V &data, const range &r) {} template<class V> void simple (vector_slice<V> &data, const range &r) {} template<class V> void hard (V &data, const typename vector_range<V>::range_type &r) {} template<class V> void hard (vector_slice<V> &data, const typename vector_slice<V>::range_type &r) {} main () { vector_slice<int> vs; simple (vs, range() ); hard (vs, range() ); } There are no problems with the functions 'simple'. It thinks the functions 'hard' are ambiguous despite the fact that the first parameter is more specialised in the second version. It seems to be disturbed by template parameter dependence of the second parameter. Anyone know of a workaround? For those that know a little more about MS compiler, or have support for it. Is the current beta of VC-8 close to the final version or is it likely that i such deeply rooted template problems are going be fixed? Michael -- ___________________________________ Michael Stevens Systems Engineering 34128 Kassel, Germany Navigation Systems, Estimation and Bayesian Filtering http://bayesclasses.sf.net ___________________________________

3 2

Library Proposal: Boost.Geom 2D and 3D Geometric Primitives
by Anis Benylloul 29 Jun '05

29 Jun '05

Hi ! It is very common for graphical libraries to declare some rectangle and point classes. In fact, all of them do that: SDL has SDL_Rect, X has XRectangle and XPoint, Qt has QRect and QPoint, Window$ has POINT and RECT (and POINTF and RECTF), rect, Rect, Rectangle, point, Point2D, Point3D, point<float> ..... etc .... And you know what ? they all are incompatible, both interface and implementation. Time to have a look at this, heu ? After few months of work here is what I have: // Code Start int main() { // point_xy is an implementation type it contains // "some implementation" of the point abtraction // Other implementaions include point_xyz<>, for 3D points typedef geom::point_xy<double> point_xy; // point<> is a wrapper class, in which you "plug" implementation types // to obtain a working ``point'' typedef geom::point<point_xy> point; // Plug, then save the result in ``point'' point pt=point_xy(3.4, 3.0), pt2=point_xy(0.2, 1.4); // Cool property access pt.x()++; pt.y()=pt2.rho(); pt.theta()+=3*pt2.y(); // Handy operator overloads pt+=pt2*4; // std::complex<> is also a possible implementation geom::point< std::complex<double> > pt_cplx=std::complex<double>(4, 6); pt2=pt_cplx-pt; // Mixed-implementation computations // point::impl() extracts the implementation out of its wrapper std::complex<double>& impl=pt_cplx.impl(); // Now for Boxes. Boxes are some generalization of rectanlges that are not always // ``flat'' typedef geom::box_xywh<int> box_xywh; // Implementation type .. typedef geom::box<box_xywh> box; // .. being plugged in a wrapper box bx, bx2; bx.xmin()=bx2.x2(); bx.width()=bx2.height(); bx.y2()=bx2.height(); // Accessing corners bx.corner< geom::x1, geom::y1>()=pt; // Displace bx.corner< geom::xmin, geom::ymax >()=bx2.corner<geom::x2, geom::y1, geom::z1>(); // Accessing the center bx.center()=bx2.center()+pt; bx2.x1()=bx.center().x(); // ..... } // Code End So, wadda you say ? -- Anis Benyelloul

3 2