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

type_info
by Kerner, Jacques 20 Dec '05

20 Dec '05

Hi, I have a type_info related problem when using boost::function on a platform that does not support rtti. boost\function\function_base.hpp(315) : error C2039: 'type_info' : is not a member of 'std' Does boost function provide something similar to the rtti policy in serialization ? How can I get around this ? Cheers, Jacques

1 0

Re: [Boost-users] Boost issues on Darwin (Mac OS X 10.4/gcc)
by Ryan McGann 19 Dec '05

19 Dec '05

(Re-posted with correct subject line) On Dec 19, 2005, at 9:00 AM, boost-users-request(a)lists.boost.org wrote: 1) The build.sh file for the boost bjam tool in the 1.33.0 and 1.33.1 release seems to have DOS line endings. I know there are prebuilt binaries of bjam up on the Web, but our build system builds it manually, and it choked on Darwin because sh didn't like the DOS line endings. I resaved the file with Unix line endings and it built fine. Did you download the tar.gz distribution? That should have Unix line endings throughout where as the .zip file has DOS line endings throughout (intensionally). Well our build system uses whichever archive is checked in. I imagine the PC folks downloaded the .zip version. I can check in a different version for the Unix folks. 2) I get errors for multiply defined symbols for the placeholder symbols declared in boost/bind/placeholders.hpp. Every file that #include <boost/bind.hpp> contains actual instances of _1, _2, etc. Changing the declarations of these in boost/bind.hpp to static (I added a __APPLE__ to the #ifdef in the middle of the file) fixes this issue, but then I get warnings for unused static symbols if I don't use the placeholder objects. This issue in particular is quite annoying. What compiler are you using? The first #if says: #if defined(__BORLANDC__) || defined(__GNUC__) isn't this the branch that gets taken? Hm in my boost/placeholders.hpp, I see #if defined(__BORLANDC__) ... #elif defined(BOOST_MSVC) || (defined(__DECCXX_VER) && __DECCXX_VER <= 60590031) || defined(__MWERKS__) ... #else ... #endif I don't have a _GCC__ anywhere in there. This is from 1.33.1 (which I just newly expanded from the .tar.gz, not the .zip). If I add a defined(__GCC__) to the first or second set of #ifdefs, it works fine. 3) The header in boost/compatibility/cpp_c_headers/cstdio does not match up with the cstdio file included with the Mac OS X dev tools. In particular it is missing a using ::snprintf, which causes problems because this cstdio file is being included BEFORE the Mac OS X version of the same file, and other C++ header files rely on std::snprtinf being declared. I fixed this at first by deleting the boost/compatibility/cpp_c_headers folder, but then ending up just deleting that single file so that OS X always used the built-in header file. Why are those headers getting included? They were intended for use only with certain broken compilers that didn't have the c-prefixed std lib headers. They're known not to work with several std conforming compilers (but shouldn't be included for these anyway). I'm not sure why they're being included. I'm guessing it's because we pass -I<path to boost> to GCC, which causes it to search inside of that directory before the standard directories get searched. I'll have to investigate that further. Thanks, Ryan

1 0

[Boost.Thread] portable thread ids and library development status
by Ben L. Perkins 19 Dec '05

19 Dec '05

I'm evaluating the difficulty involved in converting some applications that currently use an in-house cross platform library to use Boost instead. One feature these applications currently make heavy use of is the availability of a portable thread identifier that can be accessed from both inside and outside the thread. The present implementation of boost::thread lacks this feature. I searched the archives of this list and found a fairly lively discussion on this topic that took place back in 2003. Unfortunately I couldn't find any indication that it was ever resolved and apparently the original maintainer of the thread library ceased working on it about this time. I'm curious about the status of the boost::thread library now. I just downloaded boost_1_33_1 and I see from the release notes that at least minor bug fixes are still being made there. Is any more ambitious work still being done on it? Has there been any progress made toward the concept of a portable thread id? Thank you for any information you can pass along. - Ben Perkins

1 0

Assertion failure usign boost::format with Visual C++ 2005
by J.S. Otis 19 Dec '05

19 Dec '05

Hello, Here is a sample that generates an assertion failure with Visual C++ 2005. A NULL ptr is passed to std::string::append() by boost::io::detail::mk_str(). //////////////////////////////////////////////////////////////////// #include <boost/format.hpp> int main(int argc, char* argv[]) { std::string str(""); // Empty string. boost::format frmt( "%s" ); std::string res = ( frmt % str ).str(); return 0; } //////////////////////////////////////////////////////////////////// This is due to all the assert statements added in the new "secure" STL that is shipped with VC2005. But still, I don't think passing NULL to string::append() is correct anyway... Regards. J.S.Otis Software Developper InnovMetric Software Inc.

1 0

Re: [Boost-users] Graph problem -- solvable using the Boost graph library ?
by Dmitry Bufistov 19 Dec '05

19 Dec '05

>If the graph is acyclic -> it is a tree -> there is 1 and only 1 path >between any two vertices (consequently, it is both shortest and longest). >So you might as well perform breadth-first search from a starting vertex to >get all paths and distances to other vertices. BFS complexity is O(|A|) where >|A| is the number of edges in the graph. So, how "zvrba(a)globalnet.hr" point out absolutly correctly the problem could be solved using BFS (in linear time with respect to edges number), with the following visitor //////////////////code//////////////////// #include <boost/graph/adjacency_list.hpp> #include <boost/graph/breadth_first_search.hpp> using namespace boost; template < typename DistanceMap > class bfs_distance_visitor : public default_bfs_visitor { typedef typename property_traits < DistanceMap >::value_type T; public: bfs_distance_visitor(DistanceMap dmap) : m_distances(dmap) { } template <typename vertex_descriptor, typename Graph> void initialize_vertex(vertex_descriptor v, Graph& g) { m_distances[v] = 0; } template < typename Edge, typename Graph > void tree_edge(Edge e, Graph& g) { put(m_distances, target(e, g), m_distances[source(e,g)] + get(edge_weight, g, e)); } DistanceMap m_distances; }; typedef adjacency_list <listS, vecS, undirectedS, no_property, property<edge_weight_t, double> > graph_t; typedef graph_traits<graph_t>::vertex_descriptor vertex_descriptor_t; struct ltvertex { bool operator()(vertex_descriptor_t v1, vertex_descriptor_t v2) const { return unsigned(v1) < unsigned(v2); } }; template <typename TValue> struct vertex_external_property_map { typedef std::map<vertex_descriptor_t, TValue, ltvertex> property_map_type; }; typedef vertex_external_property_map<double>::property_map_type distance_map_t; int _tmain(int argc, _TCHAR* argv[]) { graph_t g; typedef associative_property_map<distance_map_t> T; T dmap; bfs_distance_visitor<associative_property_map<distance_map_t> > vis(dmap); //Now it would be good to read graph breadth_first_search(g, vertex(0, g), visitor(vis)); return 0; } ///////////////////////////////////////////////////////////////////////////// If it doesn't work then I don't know who wrote it Ну привет, --Дима

1 0

Boost Install Failure and Recommendation
by Umut Tabak 19 Dec '05

19 Dec '05

Hi everbody, I am trying to install boost and posted a message and got the reply Download "boost-jam-3.1.11-1.i386.rpm" and "boost_1_33_1.tar.gz" from http://sourceforge.net/project/showfiles.php?group_id=7586 #rpm -ivh /path/boost-jam-3.1.11-1.i386.rpm #mv /path/boost_1_33_1.tar.gz /usr/local/src/ #cd /usr/local/src #tar -zxvf boost_1_33_1.tar.gz #cd /usr/local/src/boost_1_33_1/tools/build/jam_src/ #./build.sh #cp bin.linuxx86/bjam ../../../ #cd ../../../ #./bjam "-sTOOLS=gcc" install but the very first command rpm gives a conflict message with Debian files since I am using Ubuntu which is based on Debian or am I wrong? Any comments will be appreciated. Umut TABAK

3 2

Installation Complete Steps (JeffreyHole)
by Umut TABAK 19 Dec '05

19 Dec '05

Hi, Please could you specify the steps again and could you also give the details since I am a newbie both in Linux and Boost (when you skip sth that you think easy to understand is hard for me to track). I am sorry for asking again again the same question. So I think I will directly start from step 4 and proceed as given below(I numbered the steps please check it down.) Best Regards, Umut Tabak ========================================================================= To get boost you can use either, not both. Your Linux doesn't use rpms if its debian based, so use the tar ball (boost_1_33_1.tar.gz) and unpack it with "tar -xzf boost_1_33_1.tar.gz". Umut Tabak wrote: > Hi everbody, > > I am trying to install boost and posted a message and got the reply > > Download > "boost-jam-3.1.11-1.i386.rpm" > and > "boost_1_33_1.tar.gz" > from > http://sourceforge.net/project/showfiles.php?group_id=7586 > > 1 #rpm -ivh /path/boost-jam-3.1.11-1.i386.rpm > 2 #mv /path/boost_1_33_1.tar.gz /usr/local/src/ > 3 #cd /usr/local/src > 4 #tar -zxvf boost_1_33_1.tar.gz > 5 #cd /usr/local/src/boost_1_33_1/tools/build/jam_src/ > 6 #./build.sh > 7 #cp bin.linuxx86/bjam ../../../ > 8 #cd ../../../ > 9 #./bjam "-sTOOLS=gcc" install > > but the very first command rpm gives a conflict message with Debian > files since I am using Ubuntu which is based on Debian or am I wrong? > > Any comments will be appreciated. > > Umut TABAK "Nothing is more practical than a good theory" Kurt Lewin . ----------------------------------------------------------------- Umut TABAK KULeuven - Dept. Mechanical Engineering Lab. Voertuigen techn.& Lichtgewichtcon Kasteelpark Arenberg 41, B-3001 Heverlee, Belgium Tel:+32 16 328602 Fax:+32 16 322987 http://kisi.deu.edu.tr/umut.tabak -----------------------------------------------------------------

1 0

Re: [Boost-users] [serialization]Serializing ptime instances
by Merrill Cornish 19 Dec '05

19 Dec '05

Aaarrrgh! Jeff, Thanks for the pointer. I've finally gotten used to the fact that the Documentation link on the boost.org home page doesn't include (for some reason) the documentation hidden under libs/<library name>/doc/*. Now I see that to find out about serialization, I need to not only check the various serialization documentation pages, but the library documentation to see that IT says about serialization. Anyway, that's good news. Thanks for the pointer. Merrill

1 0

[serialization]Serializing ptime instances
by Merrill Cornish 19 Dec '05

19 Dec '05

Robert, I need to serialize ptime class instances. As far as I can tell, the ptime class isn't covered yet by serialization. However, if I understand how things work, I believe I can do it myself using split member. In the save() function, I would convert my ptime instance into a string, which I then serialize as a string. In the load() function, I would retrieve the string and construct another ptime instance. The other members of the class being serialized would be handled by the usual ar & <member_name>; with the appropriate NVP wrapper, since I'm using XML archives. Is that how I should do it? Merrill

2 1

Boost issues on Darwin (Mac OS X 10.4/gcc 4)
by Ryan McGann 19 Dec '05

19 Dec '05

Hello, I am trying to use the latest release of Boost (1.33.1) on Mac OS X 10.4 with gcc 4. I am running into a couple of issues. I have worked around all of them, but since the workarounds have required editing the actual bost files, I am wondering if there's something I am missing. 1) The build.sh file for the boost bjam tool in the 1.33.0 and 1.33.1 release seems to have DOS line endings. I know there are prebuilt binaries of bjam up on the Web, but our build system builds it manually, and it choked on Darwin because sh didn't like the DOS line endings. I resaved the file with Unix line endings and it built fine. 2) I get errors for multiply defined symbols for the placeholder symbols declared in boost/bind/placeholders.hpp. Every file that #include <boost/bind.hpp> contains actual instances of _1, _2, etc. Changing the declarations of these in boost/bind.hpp to static (I added a __APPLE__ to the #ifdef in the middle of the file) fixes this issue, but then I get warnings for unused static symbols if I don't use the placeholder objects. This issue in particular is quite annoying. 3) The header in boost/compatibility/cpp_c_headers/cstdio does not match up with the cstdio file included with the Mac OS X dev tools. In particular it is missing a using ::snprintf, which causes problems because this cstdio file is being included BEFORE the Mac OS X version of the same file, and other C++ header files rely on std::snprtinf being declared. I fixed this at first by deleting the boost/compatibility/cpp_c_headers folder, but then ending up just deleting that single file so that OS X always used the built-in header file. If anybody has workarounds for any of the above issues that are better than my workarounds, please by all means let me know. Thanks for the help! Ryan

2 1