- Boost - lists.boost.org

[1.47.0][fusion] fusion::copy is undocumented?
by Akira Takahashi 06 Jul '11

06 Jul '11

Hi. boost::fusion::copy algorithm merged release, but undocumented. Should not use this in 1.47.0? I think fusion::copy is very useful. Thanks. >>======================== Akira Takahashi mailto:faithandbrave@gmail.com blog:http://d.hatena.ne.jp/faith_and_brave/

2 3

[1.47.0] Permission to merge filesystem fix
by Beman Dawes 06 Jul '11

06 Jul '11

This changeset: http://svn.boost.org/trac/boost/changeset/72855 Has now cycled through many of the regression testers. Testing is still a little light on Windows, but I've tested locally on VC++ 8, 9, and 10, and late model mingw, too. This fixes a nasty POSIX case that was throwing before main() started if the environment LANG variable was whacked. OK to merge? --Beman

3 7

how to receive UDP in Windows using boost::asio@boost1.46.0
by Jinqiang Zhang 06 Jul '11

06 Jul '11

I have two classes UDPSender and UDPReceiver. Senarios: (1)It works when I run UDPSender in QNX and UDPReceiver in Linux. (2)It doesn't work when I run UDPSender in QNX and UDPReceiver in WindowsXP.(But I see UDP datagrams using Wireshark, meaning Sender is working as in Senario(1)) (3)It partially works in Windows. i) if I use Sender sending UDP messages to 127.0.0.1, Receiver can get messages ii) if I use Sender sending UDP messages to 192.168.1.137( local address in the network ), Receiver can NOT receive. My question is: *How can I get Receiver working on Windows?* ------------------------------------------------------------------------------------------------------------------------------------------ some code: UDPReceiver::UDPReceiver( boost::asio::io_service& service, unsigned short port ) : m_service( service ), m_socket( service, udp::endpoint(udp::v4(), port)), m_peerEndpoint(), m_buffer(), m_messageReceipient() { } void UDPReceiver::SetMessageReceipient( const boost::function<void(const char*, unsigned int)>& r ) { m_messageReceipient = r; } void UDPReceiver::Start() { m_socket.async_receive_from( boost::asio::buffer(m_buffer, m_buffer.size()), m_peerEndpoint, boost::bind( &UDPReceiver::HandleReceived, shared_from_this(), boost::asio::placeholders::error, boost::asio::placeholders::bytes_transferred)); } void UDPReceiver::Stop() { m_socket.close(); } void UDPReceiver::HandleReceived( const boost::system::error_code& error, size_t bytesReceived ) { assert( !m_messageReceipient.empty() ); if( error ) { LOG( Comms, Error, "UDPReceiver:" << error.message() ); } else{ m_messageReceipient( &m_buffer.front(), bytesReceived ); m_socket.async_receive_from( boost::asio::buffer(m_buffer, m_buffer.size()), m_peerEndpoint, boost::bind( &UDPReceiver::HandleReceived, shared_from_this(), boost::asio::placeholders::error, boost::asio::placeholders::bytes_transferred)); } }

2 1

Re: [boost] Logging library
by Ivan Le Lann 06 Jul '11

06 Jul '11

----- "Tigran Hayrapetyan" <tigran.human(a)gmail.com> a écrit : > >----- "Tigran Hayrapetyan" <tigran.human(a)gmail.com> a écrit : > > > >> Hello dear Boost community > >> > >>(...) > >> Existing logging libraries which I used, are writing log messages > >> linearly, > >> just one after another. > >> In contrast, as we know, almost any application's working structure > is > >> not > >> linear, but hierarchical instead, i.e. functions which call other > >> functions, > >> and so on. > >>(...) > > > >Have you tried Boost.Log and its attributes ? > > > >http://boost-log.sourceforge.net/libs/log/doc/html/log/detailed/attributes.… > >http://boost-log.sourceforge.net/libs/log/doc/html/log/detailed/utilities.h… > > > As I understand, that features of Boost.Log library are for managing > attributes of log messages, and not log messages (or their > placements) > themselves. > So the log messages are still placed linearly, and my proposal is to > place them hierarchically. NB: I'm not a Boost.Log expert at all. I was only curious. And my understanding is that how to handle attributes is left to the sink backend. I would try writing a new sink backend that handles a named_scope attribute. http://boost-log.sourceforge.net/libs/log/doc/html/log/extension.html#log.e… Ivan

1 0

(no subject)
by Bruce Adams 05 Jul '11

05 Jul '11

Hi, This probably ought to be a FAQ. But there is currently no database library in boost. There have been some contenders in the past. I had hopes for SOCI for instance (see e.g. http://lists.boost.org/Archives/boost/2004/10/74365.php) Are there any candidates on the horizon? If not, what unrelated projects would people here recommend (or recommend against). Just for context, I am looking for a "sword against anybody who got into belief that (db) programming in the language beginning with 'J' is easier. ;) " to quote the author of SOCI in the post I mentioned. However, I'm beginning to suspect maybe it is easier in Java, not through any fault in C++ itself but in the success of the Java community versus the lack of *recognised* success in the C++ community. By the way when I search the mailing lists from the link on http://www.boost.org/community/groups.html I (and many others) get: Google Sorry... We're sorry... ... but your computer or network may be sending automated queries. To protect our users, we can't process your request right now.See Google Help for more information. Regards, Bruce.

4 4

Using clang built with MSYS/Mingw on Windows
by Edward Diener 05 Jul '11

05 Jul '11

I have been able to build clang using MSYS using the instructions on the clang web site. Everything appears to have built correctly except for a problem building the llvm sample program which I reported, and nobody has responded to. So I will ignore the problem as I see I have a clang.exe and a clang++.exe in the build/llvm/Debug+Asserts/bin directory. I have a number of questions: 1) Do I need to re-run 'configure' followed by 'make' each time I get the latest llvm and clang from SVN, or is running 'make' good enough. 2) How does clang find its headers and libraries ? In the clang User Manual under "Operating System Features and Limitations" for Mingw32 it says: "MinGW32 Clang works on some mingw32 distributions. Clang assumes directories as below; C:/mingw/include C:/mingw/lib C:/mingw/lib/gcc/mingw32/4.[3-5].0/include/c++" This is a little confusing to me. When running clang, built through MSYS, does clang understands Windows paths or does it need to be run from within MSYS and therefore understand only Linux-like paths ? The note suggests the former. 3) Can clang handle the Windows header files used by gcc in its include directory as specified above ? 4) What is the difference between clang and clang++.exe ? I do not mean to be critical because I know that many developers are working to make clang better, but the online Users Manual is pretty sparse in information, so I am hoping someone can help me here or point me to better explanations. I want to use clang to test out Boost libraries on which I am working. I heavily prefer staying on Windows so I am hoping I can use clang there. Thanks !

1 1

On #5644 (tellg returns different results for gnu libstd++ and others standard libraries for codecvt_null)
by Michael Kochetkov 05 Jul '11

05 Jul '11

Hello, please can anyone comment on https://svn.boost.org/trac/boost/ticket/5644 issue? I am really stuck with the problem and need just a resolution if it is a defect or not. And if it is then I would appreciate an approximate estimate when it is to be fixed. Thank you in advance, -- Michael Kochetkov

1 0

Phoenix V3 and Logging library help.
by Fernando Pelliccioni 05 Jul '11

05 Jul '11

Hi Thomas, all, I am researching about logging libraries. I had to discard Boost.Log ( from Andrey) because this library does not support GCC 3.4. I've seen other libraries, but none convinced me. I'm thinking of writing a simple logging library, and to avoid the use of macros, I decided to do something like this: namespace prototype1 { namespace levels { boost::phoenix::expression::argument<1>::type const trace = {{{}}}; boost::phoenix::expression::argument<1>::type const debug = {{{}}}; boost::phoenix::expression::argument<1>::type const info = {{{}}}; boost::phoenix::expression::argument<1>::type const warn = {{{}}}; boost::phoenix::expression::argument<1>::type const error = {{{}}}; boost::phoenix::expression::argument<1>::type const fatal = {{{}}}; } //namespace levels struct dynamic_logger { template <typename Pred> void log( Pred const & pred ) const { streams_type::const_iterator it = streams_.begin(); streams_type::const_iterator end = streams_.end(); for ( ; it != end; ++it ) { pred( **it ); } } void add_target ( std::ostream & ostr ) { streams_.push_back( &ostr ); } typedef std::vector< std::ostream* > streams_type; //to improve streams_type streams_; }; template <typename Logger, typename Pred> void log( Logger & logger, Pred const & pred ) { return logger.log(pred); } } //namespace prototype1 int main(/*int argc, char* argv[]*/) { { using namespace prototype1; using namespace prototype1::levels; std::ofstream outfile ("test.log"); dynamic_logger dl; dl.add_target( std::cout ); dl.add_target( outfile ); dl.log ( info << "hello" << " world!" << std::endl ); dl.log ( warn << "hello" << " world!" << std::endl ); dl.log ( error << "hello" << " world!" << std::endl ); log( dl, info "hello" << " world!" << std::endl ); //free function } return 0; } This code is a simple prototype, This code is a prototype should be improved. The questions are: 1. Does PhoenixV3 (and Proto) supports GCC 3? 2. How to make the above code write the following ... ? INFO - hello world! WARN - hello world! ERROR - hello world! INFO - hello world! Is it possible? The key is to identify the different Levels. (see namespace prototype1::levels) Please, suggestions and criticisms are welcome. Note: I do not intend to compete with Boost.Log. Thanks and regards, Fernando Pelliccioni.

3 6

[introspection] if a function is not public
by Lorenzo Caminiti 05 Jul '11

05 Jul '11

Hello all, Is there any way (SFINAE, etc) to check at run-time or at compile-time if a member function is not public? class x { public: void f ( ) {}; protected: void g ( ) {}; private: void h ( ) {}; bool is_public(...) { ... } // some implementation void check ( ) { std::cout << is_public(x::f) << std::endl; // 1 std::cout << is_public(x::g) << std::endl; // 0 std::cout << is_public(x::h) << std::endl; // 0 } }; Thanks a lot! --Lorenzo

6 9

Namespace policy: putting names in boost::detail
by Mathias Gaunard 05 Jul '11

05 Jul '11

A GSoC student and I are currently converting a library to use the namespace boost::simd. Some of the implementation details of the library are not simd-specific, and we would like to use them in some other libraries that extend boost::simd. Would it be ok to put them in the boost::detail namespace, or is that considered as bad as putting stuff in the boost namespace? We need to inject overloads and specializations into a unique namespace for boost.simd and NT2, so we could need two names, like boost::detail::dispatch and boost::detail::specialize.

5 7