October 2005 - Boost - lists.preview.boost.org

Re: [boost] Boost::Tcl
by Roman Yakovenko 03 Oct '05

03 Oct '05

> > I don't think that the same people are interested in interfacing to > *different* languages - that was the point. There are some > who want to > interface with Python, some who want to interface with Tcl, etc., but > I'm not aware of anyone who would ask for more than one language > binding. Thus, the only purpose of building a "universal" > binding would > be to have the potential of code reuse and would target not > final users, I have good example: http://www.gtk.org/bindings.html Roman Yakovenko

1 0

Partial template specialization for boost::array<T, 0> missing in CVS
by Boris 02 Oct '05

02 Oct '05

There is a partial template specialization at http://www.josuttis.com/cppcode/array.hpp for boost::array with 0 elements. However the template specialization is not in the CVS - any reason? I couldn't compile the template specialization however out of the box with VC++ 7.1: - I had to add #include <cassert>. - I had to get rid of makes_no_sense() and copy the function body into the functions which call makes_no_sense(). - I added a no-op void assign(const T& value) to boost::array<T,0> as this function is part of the interface of boost::array<T,N>. It would be nice if the template specialization is added to Boost.Array. Boris

1 0

documentation mailing list
by Arkadiy Vertleyb 02 Oct '05

02 Oct '05

Is it alive? My posts keep disappearing, and I dont see any other new messages... Regards, Arkadiy

2 2

Boost regression notification (2005-10-02 [HEAD])
by Douglas Gregor 02 Oct '05

02 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-02T05:00:14Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 119 failures in 9 libraries: concept_check (12) graph (2) mpl (1) parameter (11) serialization (30) spirit (8) thread (4) tuple (1) typeof (50) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ptr_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ref_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 lvalue_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 member_function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 noncopyable_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 std_emulation: cw-9_4 std_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_dependent_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_enum_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_int_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_multiword_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_tpl_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0

1 0

[typeof] strange failure on como
by Arkadiy Vertleyb 02 Oct '05

02 Oct '05

I got a strange failure on como in the test that had been OK for qiute a while. Does this error message make sense to anybody? Thanks, Arkadiy Test output: Bronek - typeof - function_ptr_emulation / como-4_3_3-vc7_1 Report Time: Sun, 2 Oct 2005 05:00:14 +0000 Compiler output [2005-10-02 02:40:02 UTC]: call "C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\..\Common7\Tools\vsvars32" >nul set "COMO_MS_INCLUDE=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7/include" set "PATH=;%PATH%" "como" --vc71 -c -e5 --no_version --no_prelink_verbose --display_error_numb er --long_long --diag_suppress=9,21,161,748,940,962 -D__STL_LONG_LONG -DBOO ST_TYPEOF_COMPLIANT --a -DBOOST_COMO_STRICT=1 --no_inlining /Zi /Od -D_WIN32 -DBOOST_SP_DISABLE_THREADS --exceptions -DBOOST_DISABLE_WIN32 --wchar_t -I"G:\boost" -I"G:\boost" -I"G:\boost" -o "G:\results\bin\boost\libs\typeof\test\function_ptr_emulation.test\como-4_3_ 3-vc7_1\debug\function_ptr_emulation.obj" "..\libs\typeof\test\function_ptr.cpp" como: could not rename function_ptr.int.c to _comointc.c. Failure while executing 'cl' compiler ...email Comeau for advice.

2 2

[fsm]
by Andy Little 02 Oct '05

02 Oct '05

Is fsm library not in boost 1.33.0 or have I lost it? regards Andy Little

2 5

Boost regression notification (2005-10-01 [RC_1_33_0])
by Douglas Gregor 01 Oct '05

01 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-01T15:05:12Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 79 failures in 5 libraries: foreach (1) iostreams (13) range (3) serialization (61) wave (1) |foreach| rvalue_const: vc-7_1 |iostreams| gzip_test: cw-9_5-darwin gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux mingw-3_4_2 vc-7_1 |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_exported_binary_archive: vc-6_5 test_exported_binary_archive_dll: vc-6_5 test_exported_text_archive: vc-6_5 test_exported_text_archive_dll: vc-6_5 test_exported_text_warchive: vc-6_5 test_exported_text_warchive_dll: vc-6_5 test_exported_xml_archive: vc-6_5 test_exported_xml_archive_dll: vc-6_5 test_exported_xml_warchive: vc-6_5 test_exported_xml_warchive_dll: vc-6_5 test_list_ptrs_xml_warchive_dll: gcc-3_4_3-sunos test_map_text_archive: gcc-3_4_3-sunos test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: gcc-3_4_3-sunos vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 test_split_text_warchive: gcc-3_4_3-sunos test_void_cast: gcc-3_4_3-sunos test_void_cast_dll: gcc-3_4_3-sunos |wave| testwave: gcc-3_4_3-sunos

1 0

Boost regression notification (2005-10-01 [HEAD])
by Douglas Gregor 01 Oct '05

01 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-01T05:00:11Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 120 failures in 9 libraries: concept_check (12) graph (2) mpl (1) parameter (12) serialization (30) spirit (8) thread (4) tuple (1) typeof (50) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-4_0-darwin macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ptr_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 function_ref_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 lvalue_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 member_function_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 noncopyable_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 std_emulation: cw-9_4 std_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_dependent_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_enum_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_int_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_multiword_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_tpl_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 template_type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0 type_native: cw-9_4 intel-win32-9_0 intel-win32-9_0

1 0

A GUI decomposition
by Stefan Seefeld 01 Oct '05

01 Oct '05

Given the recurring interest this topic incites, I think it is important to start by clarifying what people really mean by 'C++ GUI'. For the more practically-minded, it is a means to portably and easily write Modern C++ (TM) applications that use a graphical interface, while for others it is an occasion to Do It Right This Time (TM). Can they both be satisfied with the same API ? I believe this should be possible by making educated use of abstraction and modularisation. I'm a little reminded of the discussion around a socket / network / asyncio API, as I believe the situation is similar. This is because the methodological challenge is the same: what is needed is not a single monolithic API but in fact a set of interdependent APIs, and it is hard to draw a clear line between them. Therefor, I'd suggest we split 'GUI' into distinct modules and try to model each individually, keeping in mind that a) they all have to be able to collaborate and b) each may be implemented either in terms of a 'native' backend as well as in a OS-independent way. To get to the meat, here are the domains I think should be discussed individually: * Imaging Model =============== This module is concerned with low-level drawing primitives (2D at first, but may be extended into 3D). The associated vocabulary includes canvas, painter, graphic context ('GC'), path, pencil, etc., etc., you get the idea. * Event / Messaging Mechanism ============================= This module provides whatever it takes for individual parts of an application to exchange messages, both, graphical as well as other. Designing this module is particularly challenging if this is to be generic as some backends are rather constraining in terms of message types that can be sent / received. This module should be able to provide a uniform view on both input events ('button click', 'pointer move'), region management ('expose', 'resize'), as well as high level widget-related ('slider dragged'). * Region ('Window') Management ============================== This module is concerned with providing users with regions to draw to and receive events for, independently on what these regions actually contain. The associated vocabulary includes region, map / unmap, resize, stack, layout. While people may be inclined to think of these regions more in terms of windows, or even widgets, I believe there is good reason to keep these two concepts separate, even though in most cases there may be a one-to-one mapping between the two. (Imagine a situation where windows (which typically are screen-aligned rectangular regions) are not enough to represent regions, i.e. where you want to track stacked *shaped* graphics.) * Widgets ========= This is probably what most developers think of as 'GUI'. It's all those building blocks that have a certain style, behavior, and associated state, with more or less complex logic to keep 'view' (and possibly 'controller') separate from the 'model'. Again, I suggest this separation in the hope that it will facilitate and focus further discussion. I believe all existing GUIs support the above concepts, even though they may not be as clearly separate as I suggest here. In particular, depending on the architecture some of these aspects might be hidden, for example if the work is split into a display server and a client, where users only program the client application. As prior discussions suggest there are widely differing views on who should be in control of styling. Using different backends (or policies) developers / users can have more or less fine-grained control over these issues. A simple implementation of the high level APIs would be a slim wrapper around existing libraries, while for fine-grained control more work is needed. It would thus be an interesting exercise to see whether existing GUIs can be mapped back to the above modules I suggest. Regards, Stefan

2 1

dummy
by Andy Little 01 Oct '05

01 Oct '05

1 3