September 2005 - Boost - lists.boost.org

[Test] and [bjam] questions re DLLS
by Robert Ramey 29 Sep '05

29 Sep '05

I am making a test program in order to test the operation of the serialization library when serializable type is serialized from within a dynamically loaded DLL. I've made a DLL which serializes to a polymorphic_?archive. I'm going to make a test program which calls the DLL. Here are my questions: [Test] My DLL has included <boost/test/test_tools.hpp> and test tool macros. Things compile fine. When I try to link I get a failure because I've got not test_main - I'm using the Test Execution Monitor. Now that I think about it - its not clear at all how to address this. Suppose the above is resolved. I run my test and I get a failure in the DLL, will the exception propagate across the DLL interface into the main executable? I would hope so buf I don't know for sure. [bjam] Assuming the above issues are resolved I will have two program modules: test_dll_main and test_dll_A (dll to serialize class A). Not each bjam target lands in its own directory of the form bin/boost/libs/serialization/<test_module_name>.test/<compiler_name>/debug/threading-multi/test_module_name.exe I would guess that the dll lands in bin/boost/libs/serialization/<test_dll_name>.test/<compiler_name>/debug/threading-multi/test_dll_name.dll So in my main test module I would need something like dlopen or LoadLibrary ("bin/boost/libs/serialization/<test_module_name>.test/<compiler_name>/debug/threading-multi/test_module_name.exe") which is going to be pretty inconvenient or make sure that the test_dll is placed in the same target directory as test_main - which I don't know how to make bjam do. Is there any information on how to go about building and testing DLLS/Shared Libraries? Robert Ramey

3 3

Re: [boost] GUI
by Greer, Joe 29 Sep '05

29 Sep '05

> Thats a good point, but is that not convention only? Its not required > behaviour. > Suppose I am on an XWindows system and I want MSWindows behaviour. That > point > about locale is a good one. A sequence of user actions must map to a > state-machine that finally maps the sequence of clicks into a particular > function such as Maximise, Minimise, etc. Maybe its possible to load the > map If you want to have your application certified or branded on a particular platform, then you must follow the style guidelines. Most of the guidelines aren't written in stone, but gratuitous differences will prevent you from getting your app branded. For many, this is important. I think that any GUI should do its best to isolate the app logic from the presentation style and allow for OS specific GUI behaviors to be isolated away from the main program logic in order to facilitate easy porting to various OS-s rather than trying too hard to make it seamless, but vanilla. For example, something a simple as prompting for a file, Windows provides an API call for this that puts up the appropriate dialog box to navigate to the file and select it. The box may be different depending upon which version of Windows the app is running on, but the application doesn't have to care and they will know that the boxes are arranged in the appropriate order, have the right tab stops and shortcuts etc. Every ported app I have seen gets this wrong and it is amazing how jarring that is. I imagine that Mac users would feel the same, if they were prompted with a box that doesn't meet the Mac guidelines. This kind of thing is important for commercial apps. I am not sure how to accomplish this separation of app logic vs GUI logic, but it needs done if you want it used on non-unix systems. A GUI that is tailored to allow unix developers to port to Windows and Mac gets a big yawn from me. I would like a system that encourages developers from every platform to write their apps in a way that allows it to work everywhere and to do that, things need to be able to follow different style guidelines. I'm rambling now, so I will quit. :) Joe

1 0

Re: [boost] [cstdint] uintptr_t and intptr_t are missing
by Martin Bonner 29 Sep '05

29 Sep '05

----Original Message---- From: Joaquin M Lopez Munoz [mailto:joaquin@tid.es] > Is BOOST_HAS_INTPTR_TYPES supposed to inform whether there > are vendor-provided ::intrptr_t/::uintrptr_t types? If so, I > fail to see its utility, since boost::intrptr_t/boost::untrptr_t > can be provided universally. Not if the compiler doesn't HAVE a integral type which can hold a pointer. For example, a compiler for Intel processors with 32 bit longs, no long long, and 16:32 pointers. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

3 3

[integer] Create (u)int_natural_t
by Daryle Walker 29 Sep '05

29 Sep '05

The "int" type was supposed to match the processor's natural built-in integer processor. That was easy to maintain in the 16- and 32-bit eras, but got screwed up when we started 64-bit computing. The C and C++ communities decided to expand its integer types by keeping the current types at their 32-bit-era sizes and extended the type system with a "long long" instead of moving "int" and "long" up and adding a "short short". Now we don't have a convenient way to name the best integer type in a portable fashion. I suggest we add a "int_natural_t" typedef to <boost/cstdint.hpp> to name the best integer type (and a corresponding "uint_natural_t"). We would have to research what that type is for each compiler and/or platform combination and use #conditionals. -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

2 1

[serialization] JSON: a potential archive format?
by Daryle Walker 29 Sep '05

29 Sep '05

I was wandering around the web and saw a specification page about JSON (JavaScript Object Notation). Maybe it could be used as a new archive format for the serialization library. I looked at "Introducing JSON" @ <http://www.crockford.com/JSON/>. -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

1 0

[asio] how detect deadline_timer expired state?
by BRIDGES Dick 29 Sep '05

29 Sep '05

I'm performing an async_wait() on a deadline_timer. Based upon some independent event (e.g., a keystroke) I want to [re]set the timer and, if it was expired, 'fire' an event indicating that the system has changed state from not_running to running. Maybe I'm missing something obvious, but it seems that deadline_timer should have a method to test whether or not the timer had expired (i.e., bool expired() ). BTW: This library is a joy. When does the review period start? ;) Regards, Dick Bridges

2 1

[review] results xpressive
by Thomas Witt 28 Sep '05

28 Sep '05

Hi All, I am happy to announce that xpressive has been accepted into boost. That being said I would like to thank Eric for writing such a high quality library and all the reviewers for the significant time they spent in reviewing the library. I have received some very detailed in depth reviews of the library. This has made my job really easy. Thanks! While xpressive is accepted without conditions I'd like to point out that the test coverage should be improved in the future. Thomas Review Manager xpressive Thomas Witt witt(a)acm.org

3 2

Re: [boost] BOOST_ASSERT and __assume on MSVC
by brangdon＠cix.compulink.co.uk 28 Sep '05

28 Sep '05

In-Reply-To: <200509261722.j8QHMRms015648(a)shannonhoon.balstatdev.susq.com> stewart(a)sig.com (Rob Stewart) wrote (abridged): > > (e) is false, then the __assume tells us the sequence won't be > > executed at all, and both it and the BOOST_ASSERT can be optimised > > away. Whatever it > > If (e) is false, then BOOST_ASSERT takes some action, be it > invoking assert() or something else. Only if it's not optimised away. Here's my thinking. For clarity I'll write it like this, factoring out the common sub-expression: if (e) { BOOST_ASSERT( true ); __assume( true ); } else { BOOST_ASSERT( false ); __assume( false ); } The compiler knows that __assume(false) can never be reached so it can optimise away the whole "else" clause - provided it can prove that the BOOST_ASSERT always returns. In general it is dangerous to put other stuff in the same control block as __assume(false), because you don't know how clever the compiler will be about proving stuff like that. In this case you could argue that the compiler /cannot/ prove that BOOST_ASSERT will return; indeed in many cases it won't return. Even so I think it is a bit dangerous, but I suppose it doesn't really matter. -- Dave Harris, Nottingham, UK.

2 1

[Boost-bugs] [ boost-Bugs-1307179 ] c_local_adjustor is not thread-safe due to using localtime()
by SourceForge.net 28 Sep '05

28 Sep '05

Bugs item #1307179, was opened at 2005-09-28 19:59 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1307179&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: date_time Group: None Status: Open Resolution: None Priority: 5 Submitted By: Krzysztof Lichota (klichota) Assigned to: Jeff Garland (az_sw_dude) Summary: c_local_adjustor is not thread-safe due to using localtime() Initial Comment: c_local_adjustor is not thread-safe due to using localtime(). It should be changed to use localtime_r() or, at least, docs should mention that it is not thread-safe. The same applies to all other boost units using localtime(). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1307179&group_… ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Boost regression notification (2005-09-28 [RC_1_33_0])
by Douglas Gregor 28 Sep '05

28 Sep '05

Boost regression test failures ------------------------------ Report time: 2005-09-28T14:11:11Z 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… 76 failures in 7 libraries: bind (1) foreach (1) graph (4) iostreams (11) random (1) range (3) serialization (55) |bind| bind_cv_test: gcc-4_0-darwin |foreach| rvalue_const: vc-7_1 |graph| betweenness_centrality_test: gcc-3.4.4-linux dag_longest_paths: gcc-3.4.4-linux dijkstra_cc: gcc-3.4.4-linux relaxed_heap_test: gcc-3.4.4-linux |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-4.0.1-linux gcc-4_0-darwin intel-8.1-linux intel-9.0-linux vc-7_1 |random| random_test: gcc-3.3.6-linux |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_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: 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

1 0