- Boost - lists.boost.org

RE: [boost] Re: Customer Friendlier Boost Installation
by Brian Braatz 05 Jul '05

05 Jul '05

Wild thought- Is there a rational way to have a "environment" checker. I am NOT a bjam expert- but it would be handy if we had some cmd line program that would follow spit out all the info BJAM looks for and finds. I am slightly half cocked in this idea, but basically it would have to be enough information that you could get a better sense for what Bjam was doing Something like C:\boost\> boostenvcheck.exe ** Enviroment Report** Python is not in the path User-config.jam file is setup to use gcc, vc7.1 Etc.... I have been using boost for (has it been that long) 2 years now. Bjam still confounds me. ( I appreciate the work effort, it is a cool tool, I remain struggling with it though) (I am also a tad frustrated because I have been trying to make vc7.1 build wave for the last 5 hours) Semi-Related: I proposed (a long time ago) building a SIMPLE gui framework- with the core elements, and then making a "boost environment checker" out of that- I.e. imagine a tree control with all the types of settings and what nots, and the ability to navigate this gui to try to determine what is not set correctly. > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Lars Gullik Bjønnes > Sent: Thursday, May 26, 2005 3:27 AM > To: boost(a)lists.boost.org > Subject: [boost] Re: Customer Friendlier Boost Installation > > "Hendrik Schober" <SpamTrap(a)gmx.de> writes: > > | Lars Gullik Bjønnes <larsbj(a)gullik.net> wrote: > >> David Abrahams <dave(a)boost-consulting.com> writes: > >> > >> | We never wanted to be the sole province of experts. We always wanted > >> | widespread usage. If you want to be a member of an exclusive > >> | "experts" club this is the wrong place to find it. > >> > >> Sure. But there, imho, must be a difference expected between _users_ > >> of the libraries, and _installers_ (or packagers) of the libraries. > > > > > | How so? Shall people employ an administrator to > | install the libs they want to check out? > > No. But IMHO it should be expect that it is a bit harder to install > (and in this case it is build as well) the library than use it. > > So: Create an windows installer and then the user can use that. > > -- > Lgb > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

7 13

Re: [boost] [function_type] Tag types documentation
by Dave Gomboc 05 Jul '05

05 Jul '05

> The Function Type library uses tag types to represent a type's > attributation, such as its calling convention or wether it is > variadic. > > Tags that represent the values of a single property are called > property tags. These tags can be used to determine whether one > property of a type has a particular value. > > is_function< T, variadic > > is_function< T, default_call > > > Does it work? It's better than before. I still think you shouldn't mix "uses tag types" (plural) with "a type's attributation" (singular), but you're the author. ;-) I'd still go with "to represent attributations of types", similar to how I wrote that line previously. Oh, also, fix the spelling of "whether". > I have. Try these use cases: > > // a remove constness (of the pointee) from a member > function pointer type T > function_type<signature<T>,tag<signature<T>,non_const> >::type > > // shortcut: > function_type<T, non_const >::type > > or > > // create a (possibly decorated) function type's > variadic version > function_type<signature<T>,tag<signature<T>,variadic> >::type > > // shortcut: > function_type<T, variadic >::type Is manipulating these using MPL containers too much hassle for too little benefit? If <T, nonvariadic, variadic, variadic, nonvariadic, variadic> is really going to be the same as <T, variadic, nonvariadic, variadic>, then even testing for equivalence between tags becomes somewhat of a chore. > Well, we /could/ only allow overriding only in this very > context, however, it > would make things inconsistent and more complicated to explain, IMO. > I don't see a problem in allowing it either, because most > error situations are > pretty obvious > > a = 1; > a = 2; // <-- should this line fail to compile? No, your example above is (roughly speaking) X = tag<T, nonvariadic>; X = tag<T, variadic>; Which sequentially assigns different values to X. By writing tag<T, variadic, nonvariadic>, to my eyes you're writing something akin to "a = 1 and a = 2 (at the same time)" [One example in runtime-C++ is calling f(a=1, a=2), which does not at all guarantee that a=2 at the end of this expression! But a guru may come up with a better example.] Then, you specify a rule that says "If I assign more than one value at the same time, I really mean the last one", which is different behaviour than runtime-C++ gives. That's why this asymmetric disambiguation behaviour feels awkward to me. > plus 'tag' seldom has to be used directly by the user, anyway. > > Further there is the technical side of the story: > > tag<A,B> > > only describes a type (talking C++ type system context here) > and thus does not trigger a template instantiation. So the > error message you get would probably involve a lot of trace > (to where its PoI is) output and be questionable useful, > because of this. Explicit instantiation of templates is our friend in such cases. This is nothing new to template users. Dave

3 7

REQUEST: Sorry for the inatentiveness..
by Rene Rivera 05 Jul '05

05 Jul '05

All, Over the past two weeks I've been rather inattentive on the Boost list, actually all the lists. This was was because I was busy unexpectedly resurrecting my web, email, and cvs server after I came back from vacation. So I'm asking for a bit of help... If there's some particular email or other business I should pay attention to please point it out to me. Thanks. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

1 0

Boost regression notification (2005-06-30)
by Douglas Gregor 05 Jul '05

05 Jul '05

Boost regression test failures ------------------------------ Report time: 2005-06-30T05:35:19Z 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… 353 failures in 14 libraries: bind (1) io (2) iterator (2) numeric/ublas (21) preprocessor (1) program_options (12) python (56) random (3) regex (2) serialization (236) spirit (5) test (6) thread (2) wave (4) |bind| mem_fn_eq_test: intel-win32-8_1 |io| ios_state_unit_test: intel-win32-8_1 intel-win32-8_1 |iterator| filter_iterator_test: intel-win32-8_1 lvalue_concept_fail: intel-win32-8_1 |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| andreas_beyer: intel-win32-8_1 args: intel-win32-8_1 auto_ptr: intel-win32-8_1 back_reference: intel-win32-8_1 ben_scott1: intel-win32-8_1 bienstman1: intel-win32-8_1 bienstman2: intel-win32-8_1 bienstman3: intel-win32-8_1 builtin_converters: intel-win32-8_1 callbacks: intel-win32-8_1 const_argument: intel-win32-8_1 crossmod_exception: intel-win32-8_1 data_members: intel-win32-8_1 defaults: intel-win32-8_1 dict: intel-win32-8_1 docstring: intel-win32-8_1 embedding: intel-win32-8_1 enum: intel-win32-8_1 exception_translator: intel-win32-8_1 extract: gcc-3.3.6-linux intel-win32-8_1 implicit: intel-win32-8_1 injected: intel-win32-8_1 iterator: intel-win32-8_1 keywords: intel-win32-8_1 list: gcc-3.3.6-linux intel-win32-8_1 long: intel-win32-8_1 map_indexing_suite: intel-win32-8_1 minimal: intel-win32-8_1 multi_arg_constructor: intel-win32-8_1 nested: intel-win32-8_1 object: intel-win32-8_1 opaque: intel-win32-8_1 operators: gcc-3.3.6-linux intel-win32-8_1 pearu1: intel-win32-8_1 pickle1: intel-win32-8_1 pickle2: intel-win32-8_1 pickle3: intel-win32-8_1 pickle4: intel-win32-8_1 polymorphism: intel-win32-8_1 polymorphism2: intel-win32-8_1 properties: intel-win32-8_1 raw_ctor: intel-win32-8_1 return_arg: intel-win32-8_1 shared_ptr: intel-win32-8_1 slice: gcc-3.3.6-linux intel-win32-8_1 staticmethod: intel-win32-8_1 str: intel-win32-8_1 test_pointer_adoption: intel-win32-8_1 try: intel-win32-8_1 tuple: intel-win32-8_1 vector_indexing_suite: intel-win32-8_1 virtual_functions: intel-win32-8_1 |random| random_test: intel-win32-8_1 intel-win32-8_1 intel-win32-8_1 |regex| regex_regress: intel-win32-8_1 regex_regress_dll: 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: intel-win32-8_1 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: intel-win32-8_1 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 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 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_demo_xml_load: intel-win32-8_1 test_demo_xml_save: intel-win32-8_1 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_mi_text_warchive_dll: intel-win32-8_1 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_text_archive_dll: 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 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 test_thread_lib: cw-8_3 |wave| testwave: cw-8_3 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux

6 9

[BGL] [msvc] Warnings in pending/relaxed_heap.hpp
by Jürgen Hunold 05 Jul '05

05 Jul '05

Hi ! I'm getting e:\libraries\boost_cvs\boost\pending\relaxed_heap.hpp(49) : warning C4355: 'this' : used in base member initializer list when compiling some files using the BGL. Nasty full output zipped attached. A quick and dirty fix is attached. But I have the feeling there might be a better way to solve this. Comments ? Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Institut für Verkehrswesen, Eisenbahnbau * voice: ++49 511 762-2529 ! und -betrieb, Universität Hannover * fax : ++49 511 762-3001 ! Appelstrasse 9a, D-30167 Hannover * hunold(a)ive.uni-hannover.de ! www.ive.uni-hannover.de

3 3

Re: [boost] RegEx VC6.0 error LNK2005 errors
by Alexander Balaev 05 Jul '05

05 Jul '05

Hello, Sorry I couldn't find how to reply on the message. Actually the first workaround worked for me. I needed to place first #define BOOST_MSVC into the *right* spot. I think I misread the post initially... I will try to find if the second workaround is good although it will be hard - too many headers. Thanks much for the help, Alex. > I found the workaraund at > http://aspn.activestate.com/ASPN/Mail/Message/2509074 > but it doesn't work for me > > Could some one please help me on this.... > MSVC6.0 SP6, Window XP with the latest MS SDK. > Thanks in advance, Alex. This has been reported a couple of times, but no one has ever come up with a test case that I can reproduce, I found this: http://www.unixwiz.net/archives/2004/11/ which looks like it may be a solution, but whatever the problem is, it's of Microsoft's making and not ours. Hoping this helps, John. Thank you again, Alex. mailto:alexbalaev@yahoo.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

[Boost-bugs] [ boost-Feature Requests-1232586 ] Please add support for PDSK compilers for x64 and IA64
by SourceForge.net 05 Jul '05

05 Jul '05

Feature Requests item #1232586, was opened at 2005-07-05 00:59 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1232586&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Please add support for PDSK compilers for x64 and IA64 Initial Comment: MS Platform SDK for Windows 2003 Server SP1 contains command line compilers for x64 and IA64. It would be nice to have bjam toolsets for these compilers. Submitted by: lexeyo(a)gmail.com ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1232586&group_… ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Interfaces Library, a macro less implementation
by Joel de Guzman 05 Jul '05

05 Jul '05

Hi, I like the idea behind the Interfaces Library: http://www.kangaroologic.com/interfaces/ I need one now. I dislike the macro-based Interface Definition Language, however. I find it utterly ugly especially because interfaces should be immediately readable. IMO, the macro-based IDL is not. Here's another take (prototype) at a macro less implementation of the interfaces (see attached). Tested on VC7.1, g++ and Comeau. The biggest advantage is that the same C++ member function interface syntax is retained. This makes it very easy to understand and even allows documentation extraction tools like Doxygen to work as usual. A disadvantage is that there is some unavoidable redundancy-- a lesser price to pay, IMO. Here's a client side example: struct foo : member_function<int(int)> {}; struct bar : member_function<int(char const*)> {}; // a baz "interface" class baz : interface<foo, bar> { public: template <class T> baz(T& x) : construct(x) {} int foo(int x) { return this->call< ::foo>(x); } int bar(char const* x) { return this->call< ::bar>(x); } }; struct some_baz { int impl(foo, int x) { return x + 1; } int impl(bar, char const* s) { return std::strlen(s); } }; struct another_baz { int impl(foo, int x) { return x - 1; } int impl(bar, char const* s) { return -std::strlen(s); } }; int main() { some_baz f; baz p = f; std::cout << "p.foo(3) = " << p.foo(3) << std::endl; std::cout << "p.bar(\"hi\") = " << p.bar("hi") << std::endl; another_baz f2; p = f2; std::cout << "p.foo(3) = " << p.foo(3) << std::endl; std::cout << "p.bar(\"hi\") = " << p.bar("hi") << std::endl; } Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net #include <iostream> #include <string> #include <cstring> #include <boost/spirit/fusion/sequence/tuple.hpp> #include <boost/spirit/fusion/sequence/at.hpp> using namespace boost::fusion; template <class Sig> struct member_function; template <class RT, class A0> struct member_function<RT(A0)> { typedef RT return_type; typedef A0 arg0_type; typedef RT(*pointer_type)(void*, A0); }; template <class F0, class F1> struct interface { typedef tuple< typename F0::pointer_type , typename F1::pointer_type> vtable_type; template <class T> struct functions { template <typename F> struct forward { typedef typename F::return_type return_type; typedef typename F::arg0_type arg0_type; static return_type call(void* p, arg0_type x) { return static_cast<T*>(p)->impl(F(), x); } }; static typename interface<F0, F1>::vtable_type const* table() { static typename interface<F0, F1>::vtable_type vtable( &forward<F0>::call , &forward<F1>::call); return &vtable; // a singleton } }; template <class T> interface(T& x) : vtable(functions<T>::table()) , obj(&x) {} typedef interface<F0, F1> construct; typename boost::fusion::meta::at_c<vtable_type const, 0>::type find(F0) const { return boost::fusion::at<0>(*vtable); } typename boost::fusion::meta::at_c<vtable_type const, 1>::type find(F1) const { return boost::fusion::at<1>(*vtable); } template <typename F> typename F::return_type call(typename F::arg0_type x) { return find(F())(const_cast<void*>(obj), x); } vtable_type const* vtable; void const* obj; }; /////////////////////////////////////////////////////////////// // // Client Code // /////////////////////////////////////////////////////////////// struct foo : member_function<int(int)> {}; struct bar : member_function<int(char const*)> {}; // a baz "interface" class baz : interface<foo, bar> { public: template <class T> baz(T& x) : construct(x) {} int foo(int x) { return this->call< ::foo>(x); } int bar(char const* x) { return this->call< ::bar>(x); } }; struct some_baz { int impl(foo, int x) { return x + 1; } int impl(bar, char const* s) { return std::strlen(s); } }; struct another_baz { int impl(foo, int x) { return x - 1; } int impl(bar, char const* s) { return -std::strlen(s); } }; int main() { some_baz f; baz p = f; std::cout << "p.foo(3) = " << p.foo(3) << std::endl; std::cout << "p.bar(\"hi\") = " << p.bar("hi") << std::endl; another_baz f2; p = f2; std::cout << "p.foo(3) = " << p.foo(3) << std::endl; std::cout << "p.bar(\"hi\") = " << p.bar("hi") << std::endl; }

11 25

Co-author?
by David Abrahams 05 Jul '05

05 Jul '05

Hi Eric, I'm thinking that somebody who knows what users need has to write the Boost books. I'm a little wary of co-authoring again, but I have a lot of confidence in your ability to communicate and have been thinking of asking you about it for some time. I know you're on vacation, but I see you're still active on the lists, so I thought I'd plant the seed of the idea and see what grows there. So, what do you think about writing a series of books on Boost? -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 1

Re: [boost] static assert
by Philippe Mori 04 Jul '05

04 Jul '05

> Even though I'm surely not the first one that came up to this, I've got a > feature suggestion for the Static Assert library. > > It would probably be nice to have a variation of the macro that has a second > argument with a short description of the problem that caused the assertion. > > > For example: > > ... > #elif defined(BOOST_MSVC) > #define BOOST_STATIC_ASSERT2( B, explanation ) \ > typedef ::boost::static_assert_test<\ > sizeof(::boost::BOOST_JOIN(STATIC_ASSERTION_FAILURE__, explanation)< (bool)( > B ) >)>\ > BOOST_JOIN(boost_static_assert_typedef_, __COUNTER__) > ... > > static_assert(2 > 3, two_not_larger_than_three); > > error C2039: 'STATIC_ASSERTION_FAILURE__two_not_larger_than_three' : is not a > member of 'boost' > > > > Comments? > > Well, I tend to prefer a solution in the line of : STATIC_ASSERT_GT(2, 3); My implementation is based on conversion on template classes : template <long> struct Value { }; template <long p1, long p2, bool p3> struct ValueCond { }; #define STATIC_ASSERT_EQUAL(a, b) \ Value<(a)>(((void)0, Value<(b)>())) #define STATIC_ASSERT_GREATER(a, b) \ ValueCond<(a), (b), ((a) > (b))> \ (((void)0, ValueCond<(a), (b), true>())) Well, this solution needs some improvments : 1) Ensure it works on most compiler. It works with Visual C++ 7.1 and CodeWarrior for Palm 9.03. 2) Ensure that error message is meaningfull or try to find alternate solution for that compiler. 3) Make it BOOST compliant 4) Make it works with larger integers. Part of the solution is using the biggest integers availables at compile-time but it does still restrict the range of checks (it won't works for very big unsigned numbers). It should be done generally so that the user won't have to uses differents set of amcros for big unsignbed number as this would require the user to know the type of every constants he wants to check. In practice, this is not often a big constraint as we can always uses existing assertions for special cases and also because most check are relatively small number (for example, checking the size of a buffer). Philippe

2 1