- Boost-users - lists.boost.org

[asio] async connect vs sync connect
by Mathieu Peyréga 02 Oct '09

02 Oct '09

Hello, I have a TCP client program using boost 1.40 asio framework and a question. I have an external LAN hosted TCP server ready to accept connexions (functionnal and tested with other means) On my client side, when using the async connect function, it sometimes take up to 2-3 seconds before the connexion handler is called. If I use the synchronous connect function, it is almost immediate. Is there a way to speed up the connexion time, while using the async method ? Regards, Mathieu

1 0

[asio] deadline_timer makes wrong delay when using date command
by Bjarne Laursen 02 Oct '09

02 Oct '09

I have used a deadline_timer to generate a polling every 1 second. Unfortunely when I use the linux date command the timing is curupted. (If I set the clock back 1 min. I will be missing 60 pollings). What can I do about that? -Bjarne

4 9

[BoostCon 2010] Call for Participation
by Hartmut Kaiser 02 Oct '09

02 Oct '09

Please distribute! -------------------------------- 4th Annual Boost Conference 2010 -------------------------------- Aspen CO, USA, May 4-10, 2010, www.boostcon.com Call for participation ---------------------- We invite you to submit session proposals to the 4th Annual Boost Conference: BoostCon 2010 (Aspen CO, USA, May 10-14, 2010). Traditionally the main face-to-face event for all things Boost (www.boost.org) BoostCon 2010 will present leading speakers from the whole C++ community. From using the Boost libraries to writing and maintaining them, from evangelizing to deploying Boost within your organization, from infrastructure and process to vision and mission, and the new C++ Standard, BoostCon brings together the sessions, the colleagues, and the inspiration to support your work with C++ and Boost in particular for the next year. To reflect the breadth of the Boost community, the conference includes sessions aimed at two constituencies: Boost end-users and hard-core Boost library and tool developers. The program fosters interaction and engagement within and across those two groups, with an emphasis on hands-on, participatory sessions. Session topics -------------- Topics of interest include, but are not restricted to, the following: * General tutorial sessions introducing one or more Boost libraries * In-depth sessions on using specific Boost libraries * Case studies on using Boost * Experts panels * Advanced sessions on implementation techniques used within Boost libraries * C++0x and how it will change life for users and library writers * Development workshops to extend or enhance existing Boost libraries * Workshops on design process * Infrastructure workshops such as Build tools, Website, Testing * Concepts and Generic Programming * Hardware and infrastructure presentations focused on how libraries can make better use of the technology * Other topics likely to be of great interest to Boost users and developers Interactive and collaborative sessions are encouraged, as this is the nature of both the on-line Boost community and the style of learning and participation that has proven most successful at such events. Sessions can be tutorial based, with an emphasis on interaction and participant involvement, or workshop based, whether hands-on programming or paper-based, discussion-driven collaborative work. Session formats --------------- Presentations Presentations focus on a practitioner's ideas and experience with anything relevant to Boost and Boost users. Panels Panels feature three or four people presenting their ideas and experiences relating to Boost's relevant, controversial, emerging, or unresolved issues. Panels may be conducted in several ways, such as comparative, analytic, or historic. Tutorials Tutorials are sessions at which instructors teach conference participants specific Boost-relevant skills. Workshops Workshops provide an active arena for advancements in Boost- relevant topics. Workshops provide the opportunity for experienced practitioners to develop new ideas about a topic of common interest and experience. Author's Corner Presentations These were introduced at BoostCon 2008, and were a great success. They are short (30 minute) sessions, focusing on tips on usage and design. In addition, we're looking to uncover the hidden design gems in Boost libraries. Tool Vendors Presentations We actively encourage tool vendors and ISP's to submit proposals for a special Tool Vendors Session Track aimed at products related to Boost and C++ (compilers, libraries, tools, etc.). Other formats may also be of interest. Don't hold back a proposal just because it doesn't fit into a pigeonhole. Submitting a proposal --------------------- Standard Sessions are 90 minutes. You may submit a proposal for fractions or multiples of 90-minutes. Fractional proposals will be grouped into 90 minute sessions covering related topics. Longer sessions, such as tutorials and classes, will be assigned 90 minute, three hour (i.e. half day), or six hour (i.e. full day) time slots. Please include: * The working title. * Type of session: presentation, panel, tutorial, workshop, authors corner, vendor track, other. * A paragraph or two describing the topic covered, suitable for the conference web site. * Proposed length: 10-20 minute short talks, 45 minutes, 90 minutes, half day, full day. * Alternate lengths, if you are willing to make adjustments: 10-20 minute short-talks, 45 minutes, 90 minutes, half-day, full day. * Audience: users, developers, both. * Level: basic, intermediate, advanced. * A biography, suitable for the conference web site. * Your contact information (will not be made public). Submission details ------------------ All submissions have to be done through the EasyChair conference management system: http://www.easychair.org/conferences/?conf=boostcon10. If you have not already registered at EasyChair, you will need to do so in order to submit your proposal. All submissions will go through a peer review process. Authors are invited (but are not required) to submit PDF versions of full papers of up to 10 pages in ACM conference proceedings format (see http://www.acm.org/sigs/publications/proceedings-templates) The full papers are not required unless you want them published in the proceedings. All accepted proposals will be made available in the Association for Computing Machinery (ACM) Digital Library (approval pending). Best papers, after further reviews, will be considered to be book chapters or journal articles in a renowned journal. The session materials go on the BoostCon website and will be available to attendees. For general information on the BoostCon 2010 paper submission or the scope of technical papers solicited, please refer to the conference website at www.boostcon.com. For any other questions about the submission process or paper format, please contact the Program Committee at boostcon10(a)easychair.com. If you have any technical problems with EasyChair, please contact EasyChair for help. Note: Presenters must agree to grant a non-exclusive perpetual license to publish submitted materials, either electronically or in print, in any media related to BoostCon. Important dates --------------- Proposal submissions due: Dec 10th, 2009. Proposals decisions sent (tentative program available): Jan 15th, 2010. Fully scheduled program available: Feb 5th, 2010. Session materials due: Apr 15th, 2010. Hartmut Kaiser, email: hartmut.kaiser(a)gmail.com (Program Committee Chair) David Abrahams, email: dave(a)boostpro.com (Conference Chair) On behalf of the conference organizers

1 0

[xpressive] Calling a function with captured text as a parameter from a rule action
by Ami Ganguli 01 Oct '09

01 Oct '09

Hi all, I've been trying to wrap my head around xpressive. I've got a rule that captures some text, calls a function as part of the action. The function call works, but as soon as I try to pass my captured text as a parameter to the function, I run into a rather long and incomprehensible compilation error. Are there working examples somewhere that do this? (There are examples on calling functions and examples on using captured text in the docs, but nothing that does both) Here's the important bits of my code: My function object: struct append_element_impl { typedef void result_type; void operator()(std::string& text) const { std::cout << "appending " << text; } }; function<append_element_impl>::type const append_element = {{}}; The part of the parser that calls the function: h1 = "=" >> +blank >> * (s1= ~_ln) >> eol [append_element(as<std::string>(s1))]; I've tried various variations on this (the "as<std::string>" is a recent addition, and doesn't seem to make much difference). If I get rid of the s1 parameter in both the function and the call, then everything works as expected. The last part of the error message (the part that I sort of understand) is: /usr/local/include/boost/proto/context/default.hpp:357: error: no match for call to ‘(const append_element_impl(std::basic_string<char, std::char_traits<char>, std::allocator<char> >)’ /home/ganguli/acms/plug-ins/wikitext/wikitext.C:27: note: candidates are: void append_element_impl::operator((std::string&) const /usr/local/include/boost/proto/context/default.hpp:357: error: return-statement with a value, in function returning 'void' I'd really appreciate any pointers on this, or just some examples on how to do something similar. Cheers, Ami.

2 2

Documentation correction
by Joseph Garvin 01 Oct '09

01 Oct '09

http://www.boost.org/doc/libs/1_40_0/doc/html/boost/interprocess/open_copy_… Reads: "Tag to indicate that the resource must be only opened for reading." I assume it should read: "Tag to indicate that the resource is copy on write."

1 0

Re: [Boost-users] Problem detecting python
by Christian O'Reilly 01 Oct '09

01 Oct '09

I seem to have a problem similar to the one first spoke about in this thread, however I have it with the version 1.4.0.I try co compile boost_python library with MinGW under XP. Here is the command I use : E:\PySide_dev\boost_1_40_0>bjam toolset=gcc --with-python --debug-configuration stage And here is a part of the output I get : notice: [python-cfg] Registry indicates Python 2.5 installed at "E:\Program File s\pythonxy\python\" notice: [python-cfg] Checking interpreter command "python"... notice: [python-cfg] running command 'DIR /-C /A:S "E:\Program Files\pythonxy\py thon\python.exe" 2>&1' notice: [python-cfg] running command '"python" -c "from sys import *; print 'ver sion=%d.%d\nplatform=%s\nprefix=%s\nexec_prefix=%s\nexecutable=%s' % (version_in fo[0],version_info[1],platform,prefix,exec_prefix,executable)" 2>&1' notice: [python-cfg] ...does not invoke a working interpreter notice: [python-cfg] Checking interpreter command "E:\Program Files\pythonxy\pyt hon\python"... notice: [python-cfg] running command 'DIR /-C /A:S "E:\Program Files\pythonxy\py thon\python.exe" 2>&1' notice: [python-cfg] running command '"E:\Program Files\pythonxy\python\python" -c "from sys import *; print 'version=%d.%d\nplatform=%s\nprefix=%s\nexec_prefix =%s\nexecutable=%s' % (version_info[0],version_info[1],platform,prefix,exec_pref ix,executable)" 2>&1' notice: [python-cfg] ...does not invoke a working interpreter notice: [python-cfg] No working Python interpreter found. notice: [python-cfg] running command 'DIR /-C /A:S "E:\Program Files\pythonxy\py thon\python.exe" 2>&1' notice: [python-cfg] falling back to "python" notice: [python-cfg] Details of this Python configuration: notice: [python-cfg] interpreter command: "python" notice: [python-cfg] include path: "Include" notice: [python-cfg] library path: "\libs" notice: [python-cfg] DLL search path: "<empty>" WARNING: No python installation configured and autoconfiguration failed. See http://www.boost.org/libs/python/doc/building.html for configuration instructions or pass --without-python to suppress this message and silently skip all Boost.Python targets Notice that the informations obtained from the command '"E:\Program Files\pythonxy\python\python" -c "from sys import *; print 'version=%d.%d\nplatform=%s\nprefix=%s\nexec_prefix =%s\nexecutable=%s' % (version_info[0],version_info[1],platform,prefix,exec_pref ix,executable)" 2>&1' are correct. Any idea how to solve this? -- View this message in context: http://www.nabble.com/Problem-detecting-python-tp25153064p25670428.html Sent from the Boost - Users mailing list archive at Nabble.com.

2 2

[spirit] Cannot find assig_a in spirit 2.1
by Christian Henning 01 Oct '09

01 Oct '09

Hi there, I really liked the assign_a actor in classic spirit. Is there something like that in spirit 2.1, aka, spirit::qi? Thanks, Christian

3 9

[interprocess] problem in HPUX
by Rui Pedro Fernandes 01 Oct '09

01 Oct '09

Hi, I've been trying boost.interprocess v. 1.40 in a HP-UX 11.23 IA64 machine. Firstly I tried a 64 bit compilation of the interprocess test with aCC compiler (v. A.06.15). It failed with error: "No atomic operations implemented for this platform, sorry!". Then I used gcc 4.1.2 and compilation did succeed. Many tests got passed, however some failed with "boost::interprocess_exception::library_error". Here is an output example of both cases: >>>>>> gcc.compile.c++ ../../../bin.v2/libs/interprocess/test/named_construct_test.test/gcc-4.1.2/debug/threading-multi/named_construct_test.o "g++" -ftemplate-depth-128 -O0 -fno-inline -Wall -g -pthread -fPIC -mlp64 -DBOOST_ALL_NO_LIB=1 -DBOOST_THREAD_POSIX -DBOOST_THREAD_USE_DLL=1 -I"../../.." -c -o "../../../bin.v2/libs/interprocess/test/named_construct_test.test/gcc-4.1.2/debug/threading-multi/named_construct_test.o" "named_construct_test.cpp" gcc.link ../../../bin.v2/libs/interprocess/test/named_construct_test.test/gcc-4.1.2/debug/threading-multi/named_construct_test "g++" -o "../../../bin.v2/libs/interprocess/test/named_construct_test.test/gcc-4.1.2/debug/threading-multi/named_construct_test" "../../../bin.v2/libs/interprocess/test/named_construct_test.test/gcc-4.1.2/debug/threading-multi/named_construct_test.o" "../../../bin.v2/libs/thread/build/gcc-4.1.2/debug/threading-multi/libboost_thread-gcc41-mt-d-1_40.so.1.40.0" -lrt -g -fPIC -pthread -mlp64 testing.capture-output ../../../bin.v2/libs/interprocess/test/named_construct_test.test/gcc-4.1.2/debug/threading-multi/named_construct_test.run LD_LIBRARY_PATH="/usr/local/bin:/usr/local/lib:/usr/local/lib32:/usr/local/lib64:/usr/users/genesys/src/boost_1_40_0/bin.v2/libs/thread/build/gcc-4.1.2/debug/threading-multi:$LD_LIBRARY_PATH" export LD_LIBRARY_PATH "../../../bin.v2/libs/interprocess/test/named_construct_test.test/gcc-4.1.2/debug/threading-multi/named_construct_test" > "../../../bin.v2/libs/interprocess/test/named_construct_test.test/gcc-4.1.2/debug/threading-multi/named_construct_test.output" 2>&1 status=$? echo >> "../../../bin.v2/libs/interprocess/test/named_construct_test.test/gcc-4.1.2/debug/threading-multi/named_construct_test.output" echo EXIT STATUS: $status >> "../../../bin.v2/libs/interprocess/test/named_construct_test.test/gcc-4.1.2/debug/threading-multi/named_construct_test.output" if test $status -eq 0 ; then cp "../../../bin.v2/libs/interprocess/test/named_construct_test.test/gcc-4.1.2/debug/threading-multi/named_construct_test.output" "../../../bin.v2/libs/interprocess/test/named_construct_test.test/gcc-4.1.2/debug/threading-multi/named_construct_test.run" fi verbose=0 if test $status -ne 0 ; then verbose=1 fi if test $verbose -eq 1 ; then echo ====== BEGIN OUTPUT ====== cat "../../../bin.v2/libs/interprocess/test/named_construct_test.test/gcc-4.1.2/debug/threading-multi/named_construct_test.output" echo ====== END OUTPUT ====== fi exit $status ...on 100th target... **passed** ../../../bin.v2/libs/interprocess/test/named_construct_test.test/gcc-4.1.2/debug/threading-multi/named_construct_test.test echo passed > "../../../bin.v2/libs/interprocess/test/named_construct_test.test/gcc-4.1.2/debug/threading-multi/named_construct_test.test" gcc.compile.c++ ../../../bin.v2/libs/interprocess/test/named_mutex_test.test/gcc-4.1.2/debug/threading-multi/named_mutex_test.o "g++" -ftemplate-depth-128 -O0 -fno-inline -Wall -g -pthread -fPIC -mlp64 -DBOOST_ALL_NO_LIB=1 -DBOOST_THREAD_POSIX -DBOOST_THREAD_USE_DLL=1 -I"../../.." -c -o "../../../bin.v2/libs/interprocess/test/named_mutex_test.test/gcc-4.1.2/debug/threading-multi/named_mutex_test.o" "named_mutex_test.cpp" gcc.link ../../../bin.v2/libs/interprocess/test/named_mutex_test.test/gcc-4.1.2/debug/threading-multi/named_mutex_test "g++" -o "../../../bin.v2/libs/interprocess/test/named_mutex_test.test/gcc-4.1.2/debug/threading-multi/named_mutex_test" "../../../bin.v2/libs/interprocess/test/named_mutex_test.test/gcc-4.1.2/debug/threading-multi/named_mutex_test.o" "../../../bin.v2/libs/thread/build/gcc-4.1.2/debug/threading-multi/libboost_thread-gcc41-mt-d-1_40.so.1.40.0" -lrt -g -fPIC -pthread -mlp64 testing.capture-output ../../../bin.v2/libs/interprocess/test/named_mutex_test.test/gcc-4.1.2/debug/threading-multi/named_mutex_test.run LD_LIBRARY_PATH="/usr/local/bin:/usr/local/lib:/usr/local/lib32:/usr/local/lib64:/usr/users/genesys/src/boost_1_40_0/bin.v2/libs/thread/build/gcc-4.1.2/debug/threading-multi:$LD_LIBRARY_PATH" export LD_LIBRARY_PATH "../../../bin.v2/libs/interprocess/test/named_mutex_test.test/gcc-4.1.2/debug/threading-multi/named_mutex_test" > "../../../bin.v2/libs/interprocess/test/named_mutex_test.test/gcc-4.1.2/debug/threading-multi/named_mutex_test.output" 2>&1 status=$? echo >> "../../../bin.v2/libs/interprocess/test/named_mutex_test.test/gcc-4.1.2/debug/threading-multi/named_mutex_test.output" echo EXIT STATUS: $status >> "../../../bin.v2/libs/interprocess/test/named_mutex_test.test/gcc-4.1.2/debug/threading-multi/named_mutex_test.output" if test $status -eq 0 ; then cp "../../../bin.v2/libs/interprocess/test/named_mutex_test.test/gcc-4.1.2/debug/threading-multi/named_mutex_test.output" "../../../bin.v2/libs/interprocess/test/named_mutex_test.test/gcc-4.1.2/debug/threading-multi/named_mutex_test.run" fi verbose=0 if test $status -ne 0 ; then verbose=1 fi if test $verbose -eq 1 ; then echo ====== BEGIN OUTPUT ====== cat "../../../bin.v2/libs/interprocess/test/named_mutex_test.test/gcc-4.1.2/debug/threading-multi/named_mutex_test.output" echo ====== END OUTPUT ====== fi exit $status ====== BEGIN OUTPUT ====== create_then_open_then_open_or_create<33named_mutex_creation_test_wrapper> Failed: false file: named_creation_template.hpp line : 34 boost::interprocess_exception::library_error EXIT STATUS: 1 ====== END OUTPUT ====== ...failed testing.capture-output ../../../bin.v2/libs/interprocess/test/named_mutex_test.test/gcc-4.1.2/debug/threading-multi/named_mutex_test.run... <<<<<< Could anyone explain this error? Is it possible to overcome the problem? Thanks in advance. Rui

6 18

Re: [Boost-users] Reference count in shared_ptr
by Daniele Barzotti 01 Oct '09

01 Oct '09

On Thu 01/10/09 17:47 , Roman Perepelitsa wrote: > > In this case, is 'delete' called twice for Impl2? > > Yes. When you passed a pointer to shared_ptr, you don't own this > pointer anymore, so you shouldn't delete it manually. > Roman Perepelitsa. > Thanks Roman! Now I tested it on my skin! :-) Regards, Daniele.

1 0

Reference count in shared_ptr
by Daniele Barzotti 01 Oct '09

01 Oct '09

Hi, I've a doubt about shared_ptr... Suppose to have something like this: template class Interface {..pure virtual..} template class Impl1 : public Interface {....} template class Impl2 : public Interface {....} class A { public: Interface* GetObjPtr() { return &obj; } private: Impl2 obj; }; class B { ~B() { delete a_ptr; } B() { a_ptr = new A; Int_ptr.reset( a_ptr->GetObjPtr ); } private: A* a_ptr; shared_ptr< Interface > Int_ptr; }; Where B creates and use A on its internal. In this case, is 'delete' called twice for Impl2? (When A is destroyed and when B, and its shared_ptr, is destroyed). Thanks, Daniele.

2 1