October 2003 - Boost-users - lists.preview.boost.org

RE: [Boost-users] Re: Linking STLPort 4.3 and Boost with VC7.0
by Ben Hutchings 21 Oct '03

21 Oct '03

David Abrahams <dave(a)boost-consulting.com> wrote: <snip> > > Thanks for the tips but how do i go about "..preprocessing > > your code and looking for suspicious #includes."? > > I never debugged the preprocess level before. > > Invoke your compiler with -E instead of -c (or /E instead of /c) and > look at the #include lines for the names of old-style headers. There are no #include directives in preprocessor output. There may be #line directives or similar lines stating filenames though.

1 0

First time using the boost libs and stuck horribly
by David Kowis 21 Oct '03

21 Oct '03

First of all, apologies if this information can be found somewhere else. I couldn't find it anywhere on the internet. Now to the real problem. I'm simply trying to utilize the boost libraries (filesystem in particular) in my program. I'm just trying to even run the example programs. I'm using Visual C++ 6.0 sp5. I figured out how to compile it by including the directory where boost is. So the example program compiles perfectly fine. Then the shit hits the fan, every reference to any boost object gets an unresolved external error. I have no clue why this is happening, and the most frustrating part is I cannot find information anywhere on the internet on how to make it work. I find lots of references telling me how great it is, but I cannot use it! Dave My compile output from visual c++ 6.0: -------------------------------------------------------------------------------- Compiling... path_test.cpp Linking... LINK : warning LNK4075: ignoring /INCREMENTAL due to /DEBUGTYPE specification path_test.obj : error LNK2001: unresolved external symbol "public: __thiscall boost::filesystem::path::path(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (??0path@filesystem@boost@@QAE@ABV?$basic_s tring@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z) path_test.obj : error LNK2001: unresolved external symbol "public: __thiscall boost::filesystem::path::path(char const *,enum boost::filesystem::path_format)" (??0path@filesystem@boost@@QAE@PBDW4path_format@12@@Z) path_test.obj : error LNK2001: unresolved external symbol "public: bool __thiscall boost::filesystem::path::is_complete(void)const " (?is_complete@path@filesystem@boost@@QBE_NXZ) path_test.obj : error LNK2001: unresolved external symbol "public: bool __thiscall boost::filesystem::path::has_branch_path(void)const " (?has_branch_path@path@filesystem@boost@@QBE_NXZ) path_test.obj : error LNK2001: unresolved external symbol "public: bool __thiscall boost::filesystem::path::has_relative_path(void)const " (?has_relative_path@path@filesystem@boost@@QBE_NXZ) path_test.obj : error LNK2001: unresolved external symbol "public: bool __thiscall boost::filesystem::path::has_root_directory(void)const " (?has_root_directory@path@filesystem@boost@@QBE_NXZ) path_test.obj : error LNK2001: unresolved external symbol "public: bool __thiscall boost::filesystem::path::has_root_name(void)const " (?has_root_name@path@filesystem@boost@@QBE_NXZ) path_test.obj : error LNK2001: unresolved external symbol "public: bool __thiscall boost::filesystem::path::has_root_path(void)const " (?has_root_path@path@filesystem@boost@@QBE_NXZ) path_test.obj : error LNK2001: unresolved external symbol "public: class boost::filesystem::path __thiscall boost::filesystem::path::root_path(void)const " (?root_path@path@filesystem@boost@@QBE?AV123@XZ) path_test.obj : error LNK2001: unresolved external symbol "public: class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __thiscall boost::filesystem::path::root_directory(void)const " (?root_directory@path@filesyst em@boost@@QBE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@XZ) path_test.obj : error LNK2001: unresolved external symbol "public: class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __thiscall boost::filesystem::path::root_name(void)const " (?root_name@path@filesystem@boost@@ QBE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@XZ) path_test.obj : error LNK2001: unresolved external symbol "public: class boost::filesystem::path __thiscall boost::filesystem::path::relative_path(void)const " (?relative_path@path@filesystem@boost@@QBE?AV123@XZ) path_test.obj : error LNK2001: unresolved external symbol "public: struct boost::iterator_adaptor<struct boost::filesystem::detail::path_itr_imp,struct boost::default_iterator_policies,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const *,struct std::bidirectional_iterato r_tag,int> __thiscall boost::filesystem::path::begin(void)const " (?begin@path@filesystem@boost@@QBE?AU?$iterator_adaptor@Upath_itr_imp@detail@filesystem@boost@@Udefault_iterator_policies@4@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@st d@@ABV67@PBV67@Ubidirectional_iterator_tag@7@H@3@XZ) path_test.obj : error LNK2001: unresolved external symbol "bool __cdecl boost::filesystem::boost_directory_name(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (?boost_directory_name@filesystem@boost @@YA_NABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z) path_test.obj : error LNK2001: unresolved external symbol "bool __cdecl boost::filesystem::boost_file_name(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (?boost_file_name@filesystem@boost@@YA_NABV? $basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z) path_test.obj : error LNK2001: unresolved external symbol "bool __cdecl boost::filesystem::posix_name(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (?posix_name@filesystem@boost@@YA_NABV?$basic_str ing@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z) path_test.obj : error LNK2001: unresolved external symbol "public: class boost::filesystem::path __thiscall boost::filesystem::path::branch_path(void)const " (?branch_path@path@filesystem@boost@@QBE?AV123@XZ) path_test.obj : error LNK2001: unresolved external symbol "public: class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __thiscall boost::filesystem::path::leaf(void)const " (?leaf@path@filesystem@boost@@QBE?AV?$ba sic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@XZ) path_test.obj : error LNK2001: unresolved external symbol "class boost::filesystem::path const & __cdecl boost::filesystem::check_posix_leaf(class boost::filesystem::path const &)" (?check_posix_leaf@filesystem@boost@@YAABVpath@12@ABV312@@Z) path_test.obj : error LNK2001: unresolved external symbol "bool __cdecl boost::filesystem::exists(class boost::filesystem::path const &)" (?exists@filesystem@boost@@YA_NABVpath@12@@Z) path_test.obj : error LNK2001: unresolved external symbol "public: __thiscall boost::filesystem::path::path(char const *)" (??0path@filesystem@boost@@QAE@PBD@Z) path_test.obj : error LNK2001: unresolved external symbol "public: class boost::filesystem::path & __thiscall boost::filesystem::path::operator/=(class boost::filesystem::path const &)" (??_0path@filesystem@boost@@QAEAAV012@ABV012@@Z) path_test.obj : error LNK2001: unresolved external symbol "public: void __thiscall boost::filesystem::detail::path_itr_imp::operator++(void)" (??Epath_itr_imp@detail@filesystem@boost@@QAEXXZ) path_test.obj : error LNK2001: unresolved external symbol "public: void __thiscall boost::filesystem::detail::path_itr_imp::operator--(void)" (??Fpath_itr_imp@detail@filesystem@boost@@QAEXXZ) Debug/path_test.exe : fatal error LNK1120: 24 unresolved externals Error executing link.exe. path_test.exe - 25 error(s), 1 warning(s) _ ._ _ , _ ._ (_ ' ( ` )_ .__) ( ( ( ) `) ) _) (__ (_ (_ . _) _) ,__) `~~`\ ' . /`~~` ,::: ; ; :::, ':::::::::::::::' _____________/_ __ \____________ David Kowis Computer Programmer ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

2 5

Numeric parsing of strings
by rlyon＠comgroup.net.au 21 Oct '03

21 Oct '03

Hi, Many applications are required to parse a string/file and extract numeric values. You can use sscanf or alternatively use regexp with numeric casting templates. I suprised that boost doesn't seem to contain conversion templates like: template < typename t_target > t_target decimal_cast( const std::string& arg ){ ... }; template < typename t_target > t_target octal_cast( const std::string& arg ){ ... }; template < typename t_target > t_target hex_cast( const std::string& arg ){ ... }; When you use these type of casts with regexp, you can construct simple robust parsers for reading numeric data from files, etc ..., in just a few lines of code. The lexical_cast and numeric_cast don't seem to cover these conversions. This is much better approach than using parsing framework like spirit/antlr. Shouldn't boost have this capability. Regards

1 0

Boost.threads: can't create static libraries under linux
by Brewer, Christopher 20 Oct '03

20 Oct '03

Hello, all- For some reason bjam doesn't build the 'boost.thread' static libraries for me (the shared libraries _do_ build properly, though). There are no errors, no warnings- they just don't get built. I'm working with boost-1.30.2 on Red Hat 9 using bjam 3.1.7 (the prebuilt binary from sourceforge). I've tried executing ./configure and swapping out 'user.hpp', but this has no effect. I'm mystified. Am I missing something obvious? Regards, Chris Brewer

2 1

[BUG]: Boost MP thread crasher: thread_cleanup key not being initialized
by Bobby Thomale 20 Oct '03

20 Oct '03

I believe I have found a crashing bug in the boost thread classes on MacOS X, in the MP threads implementation. I looked at the source and I think I have figured out what is wrong and how to fix it. The thread_cleanup function, which on the MP threads implementation is called each time a boost thread exits, assumes that the "cleanup key" has been initialized. If it hasn't been initialized (ie you aren't using any thread specific storage), it still calls MPGetTaskStorageValue with the uninitialized key index. Here are the first few lines of thread_cleanup: void thread_cleanup() { cleanup_handlers* handlers = reinterpret_cast<cleanup_handlers*>( MPGetTaskStorageValue(key)); if(handlers != NULL) { ... If you have not used any thread-specific storage, key is an uninitialized variable when this gets called. Not good. It looks like for the most part, rather than puking, MPGetTaskStorageValue is returning NULL when given an uninitialized key value, at least on 10.2.x. (I am doing some testing on the upcoming 10.3 release of MacOS X and noted that thread_cleanup crashes 100% of the time on this platform - I suspect MPGetTaskStorageValue is no longer returning NULL.) Since "key" is an uninitialized variable, I would think this would have unpredictable results and would crash occasionally even on 10.2.x, whenever "key" happened to start off as a value that was already in use maybe. It seems to me that we should simply make sure that the key is inited when calling thread_cleanup like so: boost::call_once(&init_cleanup_key, once); This makes sure that the key is inited, even if get_handlers is never called. (Adding that line of code to the beginning of thread_cleanup cleared up my crashing problems on 10.3 immediately.) Is that proper use of the call_once mechanism? Anyway, my first thought was to look at the implementations of threads on the other platforms, since they don't have this call_once call in their cleanup function before accessing the key either. It looks to me like, at least in the Windows code, the cleanup function is registered for the thread only during the get_handlers function, after the key is inited. If get_handlers is never called, the cleanup function never gets registered. In the Mac implementation, however, cleanup_thread is called directly by the thread proxy object at the end of thread execution, and it gets called even if get_handlers has never been called and the key has never been initialized. Here is a patch for my proposed fix. (I am sure there are other ways of fixing this too.) Comments, anyone? *** tss.orig.cpp Mon Oct 20 13:19:44 2003 --- tss.cpp Mon Oct 20 13:19:30 2003 *************** *** 126,131 **** --- 126,133 ---- void thread_cleanup() { + boost::call_once(&init_cleanup_key, once); + cleanup_handlers* handlers = reinterpret_cast<cleanup_handlers*>( MPGetTaskStorageValue(key)); if(handlers != NULL) -- Bobby --------------------------------------------------------------------- Bobby Thomale Senior Software Developer Inoveon Corporation http://www.inoveon.com/ ---------------------------------------------------------------------

1 0

[bgl] undirected_dfs to find cut-vertices
by Stephan Höfer 20 Oct '03

20 Oct '03

Hello, I build a visitor for an undirected graph which finds the cut-vertices of a given undireted graph or subgraph. I haven't found an implementation of the algorithm in the bgl. Maybe it would have been possible to use the predecessor_recorder for that. But then all the information which can be found directly while doing the df-search we have to find after having performed that search first. The interface of the undirected_dfs function doesn't take visitors via reference, so it wasn't possible to use that function. I had to call the detail::undir_dfv_impl function instead because that function takes a visitor reference and I had to recreate a function with the behaviour of the undirected_dfs. What reasons lead to the decision to disable passing a visitor by reference directly to undirected_dfs? What reasons lead to the decision to pass a const graph to a visitor function? Some useful things are disabled by that (but maybe also some bad things). Cheers, Stephan

2 1

Inconsistency in graph Example Code, Documentation
by Thomas F. O'Connell 20 Oct '03

20 Oct '03

This is a minor point but one worth correcting for the sake of correctness and ease of following the examples. In the boost-1.30.2 distribution, the file libs/graph/example/kevin-bacon.cpp makes a reference to a "./kevin-bacon.dat" file, but the file in both the distribution and the documentation is actually kevin_bacon.dat. The only difference being '_' vs. '-'. This is easily fixed by an end-user, but it would be nice to have the examples work out of the box. -tfo

3 3

Bug in graph library transitive closure algorithm?
by Watson, Jean-paul 20 Oct '03

20 Oct '03

Is anyone aware of any bugs in the graph library 'transitive_closure' algorithm? I believe I have a concrete example that exhibits an obvious bug (in particular, missing vertices that are reachable from certain source vertices), but (1) wasn't sure if there was a work-around or some well-known avoidance tactic and (2) whether anyone was actively supporting the graph library components. Thanks! Jean-Paul Watson E-mail: jwatson(a)sandia.gov Discrete Math Dept (9215), MS 1110 Phone: (505) 845-8887 P.O. Box 5800, Sandia National Labs FAX: (505) 845-7442 Albuquerque, NM 87185-1110 USA (Old) URL: http://www.cs.colostate.edu/~watsonj <http://www.cs.colostate.edu/~watsonj>

3 2

novice question: LAPACK & uBLAS
by Derek 18 Oct '03

18 Oct '03

Hi, I am a novice to all this. I am looking for a C++ library that would let me interface with BLAS/LAPACK. The immediate problem I have is the diagonalization of a large dense symmetric (possibly hermitian) matrix. (Speed will be a consideration eventually.) I would like to use the eigenproblem solvers in LAPACK. I understand that uBLAS does not have a full interface to LAPACK yet, but it looks like it is possible to use lapack at some level. (Does anyone have an example program excerpt?) I would be grateful for any advice about whether uBLAS is suitable for this. I am also considering other libraries such as MTL and Blitz++. I will be using Intel C++ compiler and/or GNU g++ on a Linux PC. Regards Derek

2 2

Necessity of assert in iterators (as called from graph)?
by Thomas F. O'Connell 17 Oct '03

17 Oct '03

In trying to compile and run the Kevin Bacon example for graph in the 1.30.2 distribution of Boost, I was able to compile, but when I ran the executable, I got: kevin-bacon: /usr/local/boost-1.30.2/boost/token_iterator.hpp:75: void boost::detail::tokenizer_policy<Type, TokenizerFunc>::increment(Iterator&) [with Iterator = boost::iterator_adaptor<boost::detail::token_iterator_base<__gnu_cxx::__normal_iterator<const char*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, boost::detail::tokenizer_policy<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::char_delimiters_separator<char, std::char_traits<char> > >, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, const std::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const std::basic_string<char, std::char_traits<char>, std::allocator<char> >*, std::forward_iterator_tag, ptrdiff_t>, Type = std::basic_string<char, std::char_traits<char>, std::allocator<char> >, TokenizerFunc = boost::char_delimiters_separator<char, std::char_traits<char> >]: Assertion `b.base().valid_' failed. Aborted Investigating led me to comment out the asserts on lines 69 and 75 of boost/token_iterator.hpp just to test. When I rebuilt without the asserts, I was able to run my executable with no problem with seemingly correct output. What purpose do the asserts serve, and why would they be failing? -tfo

2 2