- Boost-users - lists.boost.org

ip::tcp::socket - How to check that a connection is still alive
by Jean-Sebastien Stoezel 15 Jul '08

15 Jul '08

Hello, What's the usual way of checking that a TCP/IP connection initiated on a ip::tcp::socket is still alive? Thanks, Jean

2 1

How to I specify boost::fusion::vector<something> as the type of an argument?
by Peng Yu 15 Jul '08

15 Jul '08

Hi, template <typename T, typename R> class A; I would like a template function, whose argument should be of the type like. boost::fusion::vector<A<T, R1>, A<T, R2>,...> Basically, it is a vector of A. The first template arguments of A's should be the same, but the second ones are not necessarily the same. Would you please let me know how to do this? Thanks, Peng

2 1

[graph] edge index in properties
by Mojmir Svoboda 15 Jul '08

15 Jul '08

hello, i tried to implement something like gps with usage of bgl, but i made a mistake - i am storing graph::traits<>::vertex_desctriptor and graph_traits<>::edge_descritor in vertex/edge properties as a shortcut between data and the graph. this brings a heavy dependency of the property data on the chosen graph and i am wondering how to assign some numeric vertex/edge index into these properties (because edge_descriptor is in fact pair of vertices etc). my idea is to have adjacency list that is converted into compressed sparse row graph afterwards. btw: do you use pointers in your V/E properties? i tried to and now i quite regret it because of the serialization issues. many thanks for your attention, mojmir

1 0

Building Boost on 64bit with -fPIC
by Puneet Jethalia 15 Jul '08

15 Jul '08

HI, I need to link in Boost into my shared library application. This works fine for 32bit, but is not working for 64bit. It appears that Boost is not getting built properly with -fPIC on 64bit and leads to following errors: /usr/bin/ld: vpi2.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC 'vpi2.o' has the boost .a files included within it using 'ld -r' Can someone help identify if this is a boost problem or gcc problem? I am using Boost 1.34.1, gcc 3.2.3 on RHEL4. Please let me know if any other detail is needed. Any help is highly appreciated. thanks Puneet

1 0

which regex was matched
by Peter Boot 15 Jul '08

15 Jul '08

Is there functionality included in boost::xpressive::regex_search(...) that would allow you to know which of an alternated group of expressions e.g. "aaa|bbb|ccc" matched a substring in the input ?

2 2

Boost with Darwin (Mac) gcc 4.0.1
by Mathieu Peyréga 14 Jul '08

14 Jul '08

Hello, I have an issue with i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465) it seem to appear with the keyword "check" for example on files : detail/is_dereferencable.hpp detail/is_incrementable.hpp bzip2.hpp I have some compilation like : "error: declaration does not declare anything" wich disappears if i rename the check in both first files to check_ (everywhere in the file) and check_error in the third one... (and of course in the bzip2.cpp file too then) It does not happen on the very same code with gcc-4.3.0 (mingw version) nor vc8.0 does this renaming have possible side effects I have not seen (my code compiles, links, and seems to run with the modification...) Any explainations for this ? regards, Mathieu -- http://www.incub.net/

3 5

__declspec(dllexport) cannot be used with /clr:pure or /clr:safe
by Kofi Deh 14 Jul '08

14 Jul '08

I am trying to integrate a command-line program, that uses the BOOST UBLAS library, with a Windows Forms GUI. I get the following error when I attempt to compile the code: Error 1 error C3389: __declspec(dllexport) cannot be used with /clr:pure or /clr:safe C:\Program Files\boost\boost_1_35_0\boost\serialization\void_cast_fwd.hpp 26 Error 2 error C3395: 'boost::serialization::void_cast_register' : __declspec(dllexport) cannot be applied to a function with the __clrcall calling convention C:\Program Files\boost\boost_1_35_0\boost\serialization\void_cast_fwd.hpp 30 I am not linking the program to the Boost Serialization library. I realize there have already been discussions on the use of BOOST_DLLEXPORT in the serialization library. Unfortunately, it was not stated how to solve this problem.

1 0

[preprocessor] Comparing strings in BOOST_PP_NOT_EQUAL
by Maximilian Matthe 14 Jul '08

14 Jul '08

Hi! I'm developing with preprocessor a class generator, that generates the wrapper classes needed by boost.python when you want to derive in python from polymorph c++-base classes. I would need a Macro that expands to "return" if its argument is not void. I tried the following, but that obiously does not work: #define Return(type) \ BOOST_PP_EXPR_IF(BOOST_PP_NOT_EQUAL(type, void), return) I made a workaround by adding an integer value to my Array that defines the methods signature. But that is redundant. Is there a way to achieve the behaviour above?

2 2

[preprocessor] Comparing strings in BOOST_PP_NOT_EQUAL
by Maximilian Matthe 14 Jul '08

14 Jul '08

Hi! I'm developing with preprocessor a class generator, that generates the wrapper classes needed by boost.python when you want to derive in python from polymorph c++-base classes. I would need a Macro that expands to "return" if its argument is not void. I tried the following, but that obiously does not work: #define Return(type) \ BOOST_PP_EXPR_IF(BOOST_PP_NOT_EQUAL(type, void), return) I made a workaround by adding an integer value to my Array that defines the methods signature. But that is redundant. Is there a way to achieve the behaviour above?

1 0

typo in http://www.boost.org/doc/libs/1_35_0/libs/filesystem/doc/index.htm
by Faheem Mitha 14 Jul '08

14 Jul '08

Hi, the changelog for 1.34 refers to the function is_file. However, there is no such function. Take care, Faheem. ************************************************************************ Version 1.34.0 * Internationalization, provided by class templates basic_path, basic_filesystem_error, and basic_directory_iterator. * Simplification of the path interface, including elimination of distinction between native and generic formats, and separation of name checking functionality from general path functionality. * Rationalization of predicate function design, including the addition of several new functions. * Preservation of existing user code whenever possible. Deprecated features (symbolic_link_exists(), etc.) remain available for legacy code. * Clearer specification, by reference to [POSIX-01], the ISO/IEEE Single Unix Standard, with provisions for Windows and other operating systems. * New functions status, symlink_status, is_file, is_symlink, create_hard_link, create_symlink, path member and non-member swap, path inserter, path extractor, additional path relational and "/" operator overloads, additional path member template functions taking iterator arguments. * More efficient operations when iterating over directories. * Separation within the implementation of the distinction between the native operating system path syntax and API. This is important for CYGWIN users because it allows them to build for either the Windows or POSIX API's. * Numerous small implementation fixes.

1 0