March 2007 - Boost - lists.preview.boost.org

[Ann] Boost and Google Summer of Code 2007
by John Maddock 12 Mar '07

12 Mar '07

Dear Boosters, It is a pleasure to announce that Boost will be applying as a mentoring organization for the upcoming Google Summer of Code 2007. There is a lot of preparation work to be done and little time to do it. A page has been set up at the Boost Wiki: http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?Google_Summe… which will hold a list of preliminary ideas for students to take up and use in their own applications to GSoC07. Please feel free to contribute by directly editing the Wiki page. Any questions, requests for feedback etc. can be conducted through the Boost lists. Remember that this initiative, as Boost itself, is the result of many individuals' contribution and ideas, which means we are looking forward to *your* feedback. Sincerely, John Maddock

23 60

Re: [boost] [asio] does asio supports VC6 ?
by Rodrigo Pinho Pereira de Souza 12 Mar '07

12 Mar '07

I am involved on a project in VC6, and I want to check if is that possible to use ASIO on VC6. Does anyone already tried ? Thanks Rodrigo Pinho Pereira de Souza

3 2

Re: [boost] [asio].[solaris].[1_33_1] Update regarding test cases compilation
by Gaurav.Jain＠iflexsolutions.com 12 Mar '07

12 Mar '07

Hi chris, Christopher Kohlhoff <chris <at> kohlhoff.com> writes: > > Hi Gaurav, > > I just finished uploading it: > > http://sourceforge.net/project/showfiles.php?group_id=122478 > > Hopefully it will fix the issues for Solaris and AIX. > > On Wed, 21 Feb 2007 12:02:59 +0530, Gaurav.Jain <at> iflexsolutions.com said: > > No issues at all. Would you want me to try out boost.asio on Windows > > 2003 Server (SP1) - Itanium ? > > Yes please, if it's not too much trouble. The more the merrier :) > > Cheers, > Chris Sorry for the late update regarding compiling and running test case. I have used asio_3.8.0 with boost 1.33.1. Following test cases compiled and run successfully: test basic_datagram_socket.cpp basic_deadline_timer.cpp basic_socket_acceptor.cpp basic_stream_socket.cpp buffer.cpp buffered_read_stream.cpp buffered_stream.cpp buffered_write_stream.cpp completion_condition.cpp datagram_socket_service.cpp deadline_timer.cpp deadline_timer_service.cpp error.cpp io_service.cpp is_read_buffered.cpp is_write_buffered.cpp placeholders.cpp read.cpp read_until.cpp socket_acceptor_service.cpp socket_base.cpp strand.cpp stream_socket_service.cpp time_traits.cpp write.cpp test/ip address.cpp address_v4.cpp address_v6.cpp basic_endpoint.cpp basic_resolver.cpp basic_resolver_entry.cpp basic_resolver_iterator.cpp basic_resolver_query.cpp host_name.cpp multicast.cpp resolver_query_base.cpp resolver_service.cpp tcp.cpp udp.cpp unicast.cpp v6_only.cpp Following test cases is failing while executing: multicast.cpp command line : /asio_test/ip>CC -I$HOME/1.33.1/64/include -xtarget=ultra -xarch=v 9 -D_XOPEN_SOURCE=500 -D__EXTENSIONS__ -library=stlport4 -features=tmplife -features=t mplrefstatic multicast.cpp -L$HOME/1.33.1/64/lib -lboost_system-sw -lxnet -lsocket -l nsl /asio_test/ip>./a.out Running 2 test cases... multicast.cpp(241): error in "ip_multicast_runtime::test": check !ec failed unknown location(0): fatal error in "ip_multicast_runtime::test": std::length_error: b oolean socket option resize *** 1 failure detected in test suite "ip/multicast" Also from ifconfig lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 eri0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 Cheers, Gaurav DISCLAIMER: This message contains privileged and confidential information and is intended only for an individual named. If you are not the intended recipient, you should not disseminate, distribute, store, print, copy or deliver this message. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required, please request a hard-copy version.

2 1

[asio].[aix].[1_33_1] Update regarding test cases compilation
by Gaurav.Jain＠iflexsolutions.com 12 Mar '07

12 Mar '07

Hi, Am compiling & running the BOOST ASIO test case on IBM AIX machine. The detail of this activity is as follow: Boost Version: 1_33_1 (64 bit build) Asio Version: 0.3.8 (64 bit build) Compiler Details: XL C/C++ Enterprise Edition V8.0 OS Details: AIX 5.3 List of test cases executed successfully : basic_datagram_socket.cpp basic_deadline_timer.cpp basic_socket_acceptor.cpp basic_stream_socket.cpp buffer.cpp completion_condition.cpp datagram_socket_service.cpp deadline_timer.cpp deadline_timer_service.cpp error.cpp io_service.cpp is_read_buffered.cpp is_write_buffered.cpp placeholders.cpp read.cpp read_until.cpp socket_acceptor_service.cpp strand.cpp stream_socket_service.cpp time_traits.cpp unit_test.hpp write.cpp Following test case got failed during compilation : 1. buffered_read_stream.cpp Command line : xlC_r -q64 -I$HOME/1.33.1/include/boost-1_33_1 buffered_read_stream.cpp -L$HOME/1.33.1/lib -lboost_system-xlc -lxnet -lnsl "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 176.14: 1540-0217 (S) "ss_family" is not a member of "struct sockaddr_storage". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 174.17: 1540-0700 (I) The previous message was produced while processing "boost::asio::ip::basic_endpoint<boost::asio::ip::tcp>::protocol() const". "/1.33.1/include/boost-1_33_1/boost/asio/basic_socket.hpp", line 457.8: 1540-0700 (I) The previous message was produced while processing "boost::asio::basic_socket<boost::asio::ip::tcp,boost::asio::stream_sock et_service<boost::asio::ip::tcp> >::connect(const endpoint_type &)". "buffered_read_stream.cpp", line 143.31: 1540-0700 (I) The previous message was produced while processing "test_async_operations()". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 222.14: 1540-0217 (S) "ss_family" is not a member of "struct sockaddr_storage". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 220.18: 1540-0700 (I) The previous message was produced while processing "boost::asio::ip::basic_endpoint<boost::asio::ip::tcp>::port() const". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 279.57: 1540-0700 (I) The previous message was produced while processing "boost::asio::ip::basic_endpoint<boost::asio::ip::tcp>::address(const address &)". "buffered_read_stream.cpp", line 140.18: 1540-0700 (I) The previous message was produced while processing "test_async_operations()". 2. buffered_stream.cpp Command line : xlC_r -q64 -I$HOME/1.33.1/include/boost-1_33_1 buffered_stream.cpp -L$HOME/1.33.1/lib -lboost_system-xlc -lxnet -lnsl "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 176.14: 1540-0217 (S) "ss_family" is not a member of "struct sockaddr_storage". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 174.17: 1540-0700 (I) The previous message was produced while processing "boost::asio::ip::basic_endpoint<boost::asio::ip::tcp>::protocol() const". "/1.33.1/include/boost-1_33_1/boost/asio/basic_socket.hpp", line 457.8: 1540-0700 (I) The previous message was produced while processing "boost::asio::basic_socket<boost::asio::ip::tcp,boost::asio::stream_sock et_service<boost::asio::ip::tcp> >::connect(const endpoint_type &)". "buffered_stream.cpp", line 150.31: 1540-0700 (I) The previous message was produced while processing "test_async_operations()". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 222.14: 1540-0217 (S) "ss_family" is not a member of "struct sockaddr_storage". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 220.18: 1540-0700 (I) The previous message was produced while processing "boost::asio::ip::basic_endpoint<boost::asio::ip::tcp>::port() const". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 279.57: 1540-0700 (I) The previous message was produced while processing "boost::asio::ip::basic_endpoint<boost::asio::ip::tcp>::address(const address &)". "buffered_stream.cpp", line 147.18: 1540-0700 (I) The previous message was produced while processing "test_async_operations()". 3. buffered_write_stream.cpp Command line : xlC_r -q64 -I$HOME/1.33.1/include/boost-1_33_1 buffered_write_stream.cpp -L$HOME/1.33.1/lib -lboost_system-xlc -lxnet -lnsl "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 176.14: 1540-0217 (S) "ss_family" is not a member of "struct sockaddr_storage". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 174.17: 1540-0700 (I) The previous message was produced while processing "boost::asio::ip::basic_endpoint<boost::asio::ip::tcp>::protocol() const". "/1.33.1/include/boost-1_33_1/boost/asio/basic_socket.hpp", line 457.8: 1540-0700 (I) The previous message was produced while processing "boost::asio::basic_socket<boost::asio::ip::tcp,boost::asio::stream_sock et_service<boost::asio::ip::tcp> >::connect(const endpoint_type &)". "buffered_write_stream.cpp", line 150.31: 1540-0700 (I) The previous message was produced while processing "test_async_operations()". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 222.14: 1540-0217 (S) "ss_family" is not a member of "struct sockaddr_storage". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 220.18: 1540-0700 (I) The previous message was produced while processing "boost::asio::ip::basic_endpoint<boost::asio::ip::tcp>::port() const". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 279.57: 1540-0700 (I) The previous message was produced while processing "boost::asio::ip::basic_endpoint<boost::asio::ip::tcp>::address(const address &)". "buffered_write_stream.cpp", line 147.18: 1540-0700 (I) The previous message was produced while processing "test_async_operations()". 4. socket_base.cpp Command line : xlC_r -q64 -I$HOME/1.33.1/include/boost-1_33_1 socket_base.cpp -L$HOME/1.33.1/lib -lboost_system-xlc -lxnet -lnsl "socket_base.cpp", line 38.5: 1540-0600 (S) The reference to "ip" is ambiguous. "/usr/include/netinet/ip.h", line 141.8: 1540-0425 (I) "ip" is defined on line 141 of "/usr/include/netinet/ip.h". "/1.33.1/include/boost-1_33_1/boost/asio/ip/v6_only.hpp", line 24.11: 1540-0425 (I) "boost::asio::ip" is defined on line 24 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/v6_only.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/unicast.hpp", line 29.11: 1540-0425 (I) "boost::asio::ip" is defined on line 29 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/unicast.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/udp.hpp", line 29.11: 1540-0425 (I) "boost::asio::ip" is defined on line 29 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/udp.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/tcp.hpp", line 32.11: 1540-0425 (I) "boost::asio::ip" is defined on line 32 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/tcp.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/multicast.hpp", line 29.11: 1540-0425 (I) "boost::asio::ip" is defined on line 29 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/multicast.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/detail/socket_option.hpp", line 32.11: 1540-0425 (I) "boost::asio::ip" is defined on line 32 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/detail/socket_option.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/host_name.hpp", line 30.11: 1540-0425 (I) "boost::asio::ip" is defined on line 30 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/host_name.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_resolver_query.hpp", line 30.11: 1540-0425 (I) "boost::asio::ip" is defined on line 30 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_resolver_query.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/resolver_query_base.hpp", line 29.11: 1540-0425 (I) "boost::asio::ip" is defined on line 29 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/resolver_query_base.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_resolver_iterator.hpp" , line 34.11: 1540-0425 (I) "boost::asio::ip" is defined on line 34 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_resolver_iterator.hpp" . "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_resolver_entry.hpp", line 26.11: 1540-0425 (I) "boost::asio::ip" is defined on line 26 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_resolver_entry.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_resolver.hpp", line 27.11: 1540-0425 (I) "boost::asio::ip" is defined on line 27 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_resolver.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/resolver_service.hpp", line 27.11: 1540-0425 (I) "boost::asio::ip" is defined on line 27 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/resolver_service.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 36.11: 1540-0425 (I) "boost::asio::ip" is defined on line 36 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/address.hpp", line 33.11: 1540-0425 (I) "boost::asio::ip" is defined on line 33 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/address.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/address_v6.hpp", line 37.11:1540-0425 (I) "boost::asio::ip" is defined on line 37 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/address_v6.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/address_v4.hpp", line 33.11:1540-0425 (I) "boost::asio::ip" is defined on line 33 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/address_v4.hpp". "socket_base.cpp", line 199.3: 1540-0600 (S) The reference to "ip" is ambiguous. "/usr/include/netinet/ip.h", line 141.8: 1540-0425 (I) "ip" is defined on line 141 of "/usr/include/netinet/ip.h". "/1.33.1/include/boost-1_33_1/boost/asio/ip/v6_only.hpp", line 24.11: 1540-0425 (I) "boost::asio::ip" is defined on line 24 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/v6_only.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/unicast.hpp", line 29.11: 1540-0425 (I) "boost::asio::ip" is defined on line 29 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/unicast.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/udp.hpp", line 29.11: 1540-0425 (I) "boost::asio::ip" is defined on line 29 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/udp.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/tcp.hpp", line 32.11: 1540-0425 (I) "boost::asio::ip" is defined on line 32 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/tcp.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/multicast.hpp", line 29.11: 1540-0425 (I) "boost::asio::ip" is defined on line 29 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/multicast.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/detail/socket_option.hpp", line 32.11: 1540-0425 (I) "boost::asio::ip" is defined on line 32 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/detail/socket_option.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/host_name.hpp", line 30.11: "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_resolver_iterator.hpp" , line 34.11: 1540-0425 (I) "boost::asio::ip" is defined on line 34 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_resolver_iterator.hpp" . "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_resolver_entry.hpp", line 26.11: 1540-0425 (I) "boost::asio::ip" is defined on line 26 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_resolver_entry.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_resolver.hpp", line 27.11: 1540-0425 (I) "boost::asio::ip" is defined on line 27 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_resolver.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/resolver_service.hpp", line 27.11: 1540-0425 (I) "boost::asio::ip" is defined on line 27 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/resolver_service.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line 36.11: 1540-0425 (I) "boost::asio::ip" is defined on line 36 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/address.hpp", line 33.11: 1540-0425 (I) "boost::asio::ip" is defined on line 33 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/address.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/address_v6.hpp", line 37.11:1540-0425 (I) "boost::asio::ip" is defined on line 37 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/address_v6.hpp". "/1.33.1/include/boost-1_33_1/boost/asio/ip/address_v4.hpp", line 33.11:1540-0425 (I) "boost::asio::ip" is defined on line 33 of "/1.33.1/include/boost-1_33_1/boost/asio/ip/address_v4.hpp". Regards, Gaurav DISCLAIMER: This message contains privileged and confidential information and is intended only for an individual named. If you are not the intended recipient, you should not disseminate, distribute, store, print, copy or deliver this message. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required, please request a hard-copy version.

2 1

Proposal for a precise STL-based garbage collection library
by Achilleas Margaritis 12 Mar '07

12 Mar '07

Dear Boost developers, I have posted in the Vault a small library (named "CPPGC") that implements a precise garbage collector for C++. You can find it here: http://www.boost-consulting.com/vault/index.php?PHPSESSID=hqle9ubanl575jgl8… The zipped file contains the following readme file (along with the sources and an example): --BEGIN README.TXT-- Introduction ------------ CPPGC is a garbage collection library for C++. It has the following features: 1) precise collector. 2) uses the mark & sweep algorithm. 3) supports pointers to middle of objects. 4) supports arrays of objects. 5) uses only standard C++; no platform-specific code. 6) it can be used to retrofit non-GC'd programs with GC capabilities. 7) very small (under 500 lines of code). Usage ----- Include the following files in your project: cppgc.hpp cppgc.cpp Use the following code to include GC functionality: #include "cppgc.hpp" using namespace cppgc; Wrap your classes and pointers inside the class gc<T>. For example: gc<std::list<int> *> gc_list = new gc<std::list<int> >; gc_list->push_back(10); class Foo { public: gc<Foo *> m_other; }; gc<Foo *> foo1 = new gc<Foo>[10]; foo1[5].m_other = new gc<Foo>; gc<Foo> foo2[3]; foo2[1].m_other = foo1; Portability ----------- As we speak (March 2007), the classes hash_multimap, hash_set are not yet part of the std namespace. But it will be, and most compilers offer these classes in their STL implementation anyway. The code is currently tested under Visual C++ 2005, so the classes hash_multimap and hash_set are found in the stdext namespace. If you use a different compiler, feel free to replace the following code: using namespace stdext; with the namespace your compiler has for the hash classes. Threads ------- Threads are not supported. Future versions may support multithreading by providing a set of functions the library user can fill with the appropriate environment-specific code which allow the operation of the collector in a multithreaded environment. Internals --------- The idea behind the library is very simple: In order to know where the collector's pointers are, the collector maintains a memory map. The first entry of the memory map is all the memory (from 0x00000000 to 0xFFFFFFFF); this entry contains the root set. When an object is allocated on the heap, a relevant memory region entry is added to the memory map. When a pointer is created, it adds itself to the relevant memory map entry. Upon destruction, a pointer removes itself from its memory map entry. When a heap-allocated object is destroyed, the memory region entry of the object is removed from the memory map. If a pointer is not a member of a heap-allocated block, then it is added to the first entry of the memory map, which is the root set. The class used for the memory map is a hash_multimap, which allows efficient lookup of a memory region based on an memory address. This allows for pointers to the middle of blocks. A multimap is used instead of a map because keys (i.e. memory regions) can overlap one another. The collector is a classic mark & sweep implementation with 2 phases: phase 1: The graph of objects is traversed in order to mark the objects as reachable. The scanning starts from the root set, i.e. the first entry of the memory map. phase 2: the heap blocks are traversed; blocks that are not touched are deleted. A collection happens automatically when the collector's memory limit is exceeded or manually when the user invokes the 'collect_garbage' function. Performance ----------- It is not the fastest thing around, but it is better than nothing :-). Since it uses a hash map for its memory region, lookup is an O(1) operation on average (or so says the theory). It can be a nice altenative for projects that do not have great expectations on performance or where a commercial collector is not available. Notes ----- The file 'main.cpp' contains an example. --END README.TXT-- Please feel free to suggest improvements, post critisisms, discuss anything you want about it. Thank you in advance. Achilleas Margaritis

3 2

[1.34.0] Optional Regressions
by Thomas Witt 12 Mar '07

12 Mar '07

Fernando, Optional still fails on various msvc flavours. Any idea what's going on? Thomas -- Thomas Witt witt(a)acm.org

5 7

[HEAD] Ambiguity with function_traits use of `detail::`
by Dean Michael Berris 12 Mar '07

12 Mar '07

In MSVC 8.0, when using function_traits<>, the use of "detail::" is made ambiguous with fusion's "detail::" namespace. Attached diff implements a trivial fix. HTH -- Dean Michael C. Berris http://cplusplus-soup.blogspot.com/ mikhailberis AT gmail DOT com +63 928 7291459

1 0

[filesystem] Feature or bug ? 'portable filenames', again.
by Stefan Seefeld 12 Mar '07

12 Mar '07

Hi there, for the nth time I've seen this question on IRC, without being able to provide a solution: "i'm having trouble with boost filesystem... when I call " boost::filesystem::create_directory("/.test") ", I get the error "what(): boost::filesystem::path: invalid name ".test" in path: "/.test""... how can I create a directory hidden with .?" Since I have run into similar issues in the past, I'm taking this complaint to the list now. Is there a solution for this issue ? Does anybody care at all ? I find it very sad that due to this and similar issues users are turned away from boost_filesystem, as they can't use the library with *their* choice of filenames that works fine on *their* platform. The portability guide on http://boost.org/libs/filesystem/doc/portability_guide.htm lists as rationale: "...applications which must be portable to a wide variety of platforms...". However, how may people actually care for this level of portability ? Why should an ordinary GNU/Linux (or Windows, for that matter) user care for OpenVMS compatibility ?? Thanks, Stefan -- ...ich hab' noch einen Koffer in Berlin...

2 1

[wave] resetting input stream during the lifetime of a wave::context
by Stefan Seefeld 12 Mar '07

12 Mar '07

Hi there, I'm using boost::wave to implement a C/C++ preprocessor for the Synopsis (http://synopsis.fresco.org/) project. I have just been asked for support of the '-include' command line option, which, for typical compilers, means to preload an include file before parsing the actual input. I wonder how to implement that with wave. The wave::context<> constructor expects two input iterators (begin and end) which it will use during parsing. Relying only on this would mean I have to write my own iterators (or wrapper container) that is able to switch from one input source (the one specified by '-include') to the next (the actual input file). However, I believe there is a lot of value in wave::context<> being able to do that internally (either, by allowing to reassign a new pair of iterators, or by providing a copy constructor for the context that creates a new context from a new pair of iterators, but inherits the state of an existing context). Does anything like this exist ? Are there plans to support such use cases ? Many thanks, Stefan -- ...ich hab' noch einen Koffer in Berlin...

2 7

Re: [boost] boost] [interprocess] [Shared memory] STL containers and boost interprocess allocators
by Phil Endecott 11 Mar '07

11 Mar '07

> Is it possible to use boost interprocess' shared > memory allocator with the normal STL containers that > come with standard C++ build environments (gcc on > Linux and Solaris, Visual C++ on Windows, etc.)? I > know that there might be an issue with some STL > containers not properly supporting encapsulated > pointers that handle offset differences in memory > addresses. Is this the reason why interprocess has its > own containers? You might like to have a look at this thread where I asked the GNU libstdc++ people about this: http://thread.gmane.org/gmane.comp.gcc.libstdc++.devel/12919 This pre-dates Boost's shared memory library which I now use. Phil.

3 5