- Boost - lists.boost.org

[chrono] Split into Stopwatches, Chrono, Ratio and TypeTraits.ext
by vicente.botet 20 Sep '10

20 Sep '10

Hi, As requested in this ML I have splited Boost.Chrono into 4 libraries * Boost.TypeTraits.Ext: contains the C++0x common_type and add_rvalue reference traits classes and the declval utility function * Boost Ratio: contains the C++0x ratio class * Boost.Chrono: contains the C++0x chrono library + process and thread clocks * Boost.Stopwatches: time measure and reporting More information on these libraries can be found in https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Type… https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Ratio https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Chro… https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Stop… Please let me know if you prefer separated reviews for each library. Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

6 14

Connection refused after close then open
by Doak, Roger (GE Healthcare) 20 Sep '10

20 Sep '10

Hi I'm trying to limit the connections made to the server. So after creating the acceptor and accepting MAX connections I closed the acceptor. If there is a better way please let me know. Further connections are properly rejected. However after one of the connections is closed by the client I attempt to re-open the acceptor but further connections are still rejected? Create and open: m_acceptor(m_ioService, m_endpoint = resolve(m_ioService, host, port), true) Async accept: m_acceptor.async_accept(connection->socket(), boost::bind(&IpServer::handleAccept, this, aph::error, connection)); Close after max connections: m_acceptor.close(); Reopen when a connection is available: m_acceptor.open(m_endpoint.protocol()); m_acceptor.set_option(boost::asio::ip::tcp::acceptor::reuse_address(true )); m_acceptor.bind(m_endpoint); m_acceptor.listen(); m_acceptor.async_accept(connection->socket(), boost::bind(&IpServer::handleAccept, this, aph::error, connection)); Thank you for your time. Roger

1 0

[Locale] Link errors
by Alexander Lamaison 20 Sep '10

20 Sep '10

I'm getting link errors with the latest Boost.Locale (v2.91) when trying to use the Win32 backend: [ 34%] Building CXX object CMakeFiles/boost_locale.dir/libs/locale/src/win32/win _backend.cpp.obj win_backend.cpp Linking CXX shared library boost_locale.dll Creating library boost_locale.lib and object boost_locale.exp win_backend.cpp.obj : error LNK2019: unresolved external symbol "unsigned int __ cdecl boost::locale::impl_win::locale_to_lcid(class std::basic_string<char,struc t std::char_traits<char>,class std::allocator<char> > const &)" (?locale_to_lcid @impl_win@locale@boost@@YAIABV?$basic_string@DU?$char_traits@D@std@@V?$allocator @D@2@@std@@@Z) referenced in function "public: __thiscall boost::locale::impl_wi n::winlocale::winlocale(class std::basic_string<char,struct std::char_traits<cha r>,class std::allocator<char> > const &)" (??0winlocale@impl_win@locale@boost@@Q AE@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z) boost_locale.dll : fatal error LNK1120: 1 unresolved externals I configured CMake as such: boost_locale_v2.91>cmake -G "NMake Makefiles" -DDISABLE_ICU=ON -DDISABLE_STD_BACKEND=ON -DCMAKE_INCLUDE_PATH="C:\boost" Where Boost is version 1.42. This is on Windows 7 32-bit. Any ideas? Alex -- Easy SFTP for Windows Explorer (http://www.swish-sftp.org)

2 4

[Review] Formal Review: Boost.Move
by OvermindDL1 19 Sep '10

19 Sep '10

Greetings Boost Developers and Users, It's my pleasure to announce that the review of Ion Gaztañagas' Move library starts May 10th and lasts until May 24th, 2010, unless an extension occurs. What is it? =========== The Boost.Move library would supply an emulated C++1x Move semantics interface, aka RValue References, allowing for a wide variety of easy to use and easy to add in optimization abilities. The most used function it would add would be: val_b = boost::move( val_a ); Which would move val_a to val_b; val_a should not be used after this line. This semantic allows for a vast amount of optimizations, especially in regards to temporaries, see the documentation for further examples and use. Other patterns emulated are && rvalue references for functions/members and constructors. There are also a number of STL containers in the sandbox that support move semantics using this library for higher efficiency. Getting the library =================== The latest version of this library may be downloaded from SVN: http://svn.boost.org/svn/boost/sandbox/move/ and the docs may be viewed here Docs: http://igaztanaga.drivehq.com/libs/move/doc/html/index.html and do note, this library is header-only and is designed to be absolutely generic to be useful in all areas of C++ programming. Writing a review ================ If you feel this is an interesting library, then please submit your review to the developer list (preferably), or to the review manager. Here are some questions you might want to answer in your review: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick - reading? In-depth study? - Are you knowledgeable about the problem domain? And finally, every review should answer this question: - Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Special considerations ====================== If you want or need a primer on the subject, please look at the working draft for C++1x. This linked site has also been shown to be quite useful in describing move usefulness: Want Speed? Pass by Value.: http://cpp-next.com/archive/2009/08/want-speed-pass-by-value/ Move It With Rvalue References: http://cpp-next.com/archive/2009/09/move-it-with-rvalue-references/ And there are further links in that series, but those two will get you started in the domain. Best regards, OvermindDL1, Review Manager (Boost.Move)

15 78

Re: [boost] [serialization] Must the objects being serialized outlive the archive?
by Chris Yuen 18 Sep '10

18 Sep '10

Jeff Flinn wrote: > IIUC, tracked objects have their addresses place in a map, so that > subsequent serialized pointers of the same value are serialized as a > reference to the original object at that address, rather than > serializing another copy of the object. That was spot on! I did a couple of tests and I think I've confirmed this is indeed the behavior and the reason why data gets corrupt. On my platform (MSVC), new data gets allocated to the last free pointer's address and that confuses boost::serialization. >From your understanding, doesn't that basically means the "objects being serialized must outlive the archive"? Since there's no way to tell "new" to not allocate objects at an older address unless I keep objects there. So basically I must keep all data in memory until the serialization process is complete. I tried to think hard about this. Do you see any workaround to this issue so that I don't have to effectively double the memory usage? (Maybe have boost::serialization write things out immediately and clear the internal cached pointers)? Maybe boost::serialization should provide that command or some kind of "flush" command? Best regards, Chris Yuen

3 2

[function] Question on semantics of boost::function
by David Sankel 18 Sep '10

18 Sep '10

Is a boost::function<void (int)> semantically different from a boost::function<void (int &)> or a boost::function<void (const int)>? David -- David Sankel Sankel Software www.sankelsoftware.com 585 617 4748 (Office)

3 2

Re: [boost] [serialization] Must the objects being serialized outlive the archive?
by Brian Wood 17 Sep '10

17 Sep '10

Robert Ramey: > This would work. What won't work is > > { > boost::scoped_ptr<Strings> s; > const Strings * s = new Strings("Hello", "World")); > const * x = s; > oa << s; > delete s; > oa << x; > ... > } Be sure to add the --automagically flag to get that to build. > Your making this way too hard, just look at the examples and tests to see > that all you have to do is serialize though a base class pointer. You are being sloppy. But thanks for stopping the top posting. Brian Wood Ebenezer Enterprises http://webEbenezer.net

1 0

Re: [boost] [serialization] Must the objects being serialized outlive the archive?
by Chris Yuen 17 Sep '10

17 Sep '10

Robert, > It is a fundamental concept that saving data to an archive should > not alter the data. In many cases this is detected at compile time > and a warning is issued. As noted in another post, you might > snooker the system by suppressing tracking, I don't really understand. Why does the tracking has something to do with the object's lifetime? Doesn't boost::serialization has all the information it needs (tracking info, data, etc.) when I call "oa << base_ptr"? Isn't it possible to just write out everything to the stream? > But I'm intrigued why you want to do this? Why don't you just use > { > std::ofstream stream(kFilename, std::ios::binary); > boost::archive::text_oarchive oa(stream); > > { > const Strings s("Hello", "World")); > oa << s > } > ... > } As you can see from the code example, I want to be able to deserialize a list of these "commands" from the base pointer, because I actually have hundreds of these polymorphic commands and they need to each have a virtual "Execute()" method so that they know how to apply themselve to an "Actioner." (Instead of using a giant switch-case in the Actioner to identify each command) I figured it's better than using a magic number, opcode approach since boost::serialization already provides tracking. I was under the impression that if I want to deserialize using a base pointer, I must also serialize via the base pointer, is that correct? So I guess the below won't work with the original deserialization code? > { > boost::scoped_ptr<Strings> s; > const Strings * s = new Strings("Hello", "World")); > oa << s; > .... // same for all the other stuff > // s deleted as it goes out of scope > } Best regards, Chris Yuen

3 2

developer guidelines
by Lorenzo Caminiti 17 Sep '10

17 Sep '10

Hello all, This question might be trivial but I would like to confirm: What are the best/latest documents to read in order to develop a Boost library? I would be interested on how to: 1) Write code compliant to Boost coding guidelines. 2) Write documentation. 3) Write tests. 4) Write examples. 5) Integrate code within Boost files structure. 6) Integrate code within Boost build system. Thank you very much. -- Lorenzo

2 1

[local_function] any interest in a LocalFunction library?
by Lorenzo Caminiti 17 Sep '10

17 Sep '10

Hello all, Is there interest in a library that implement local functions for C++? Boost.LocalFunction (PROPOSAL DRAFT) This library allows to define and invoke a function locally within a code block. In addition to the parameters that can be passed to the function as usual upon its invocation, any variable within scope can be /binded/ to the local function declaration and used by the local function definition code. MOTIVATING EXAMPLE Consider the following example: #include <boost/local_function.hpp> class c { public: c(double const& x): x_(x) {} void f(double& x) { double y = x * 10.0; bool r; { double z = x * 100.0; // Local function definition. BOOST_LOCAL_FUNCTION( (bool) (l)( (char* const)(a) // Usual non-binded param. (bool)(b) // Another usual non-binded param. (binded)( (&x) // Binded param by reference. (const& x_) // Binded param by const reference. (y) // Binded param by value (copy). (const z) // Binded param by const value (copy) (const this) // Binded const object (by pointer). // (this) // Or, binded non-const object. ) ) ) { // Use `this_` here (not `this`) to access binded object. assert( this_->eq(x_) ); ... // Local function definition code. } BOOST_LOCAL_FUNCTION_END // Local function call only specifies non-binded params. bool r1 = BOOST_LOCAL_FUNCTION_CALL(l)("hello", true); bool r2 = BOOST_LOCAL_FUNCTION_CALL(l)("bye", false); r = r1 || r2; } // Local function goes out of scope here. ... } bool eq(double const& x) const { return x_ == x; } private: double x_; }; Note the following: 1) The local function `l` is only defined locally within a code block of the function `f`. 2) The parameter `x` of the function `f`, the member variable `x_`, the local variables `y` and `z`, and the object `this` are binded to the declaration of the local function. Therefore, they can all be used by the local function definition code even if they are not explicitly passed to the local function when it is invoked. (Also note that the binding syntax conveniently does not require the user to specify the types of the binded parameters but just their /binding-qualified/ names.) 3) The local function can be invoked (multiple times) from within the scope of its declaration. As usual, each invocation specifies the non-binded parameters and, for non-void functions, it returns the function result value. BACKGROUND I have not yet implemented Boost.LocalFunction. I will be implementing local-function features as part of Boost.Contract development (in order to support constant-correct block invariants and loop variants). I am probing for interest to understand how much effort I shall invest in making the local-function features a standalone library like Boost.LocalFunction separated from Boost.Contract. On Thu, Apr 15, 2010 at 7:02 PM, Alexander Nasonov <alnsn(a)yandex.ru> wrote: > vicente.botet wrote: >> VBE> Boost.ScopeExit showed a technique that can be used to >> emulate local functions. Alexander proposed long time ago to provide >> it independently from ScopeExit but to my knowledge this has not >> been done. > > Sorry for the late reply, I'm not following every boost thread, I got > this message via google alerts. > > Yes, this has not been done. Local function can borrow argument > binding syntax from ScopeExit but there are other things I need to think > of. For instance, in > > int BOOST_LOCAL_FUNCTION(f, > (BOOST_LOCAL_FUNCTION_BIND( (a)(&b) ), int c)) { > // ... > } BOOST_LOCAL_FUNCTION_END > > syntax, is there any way to shorten BOOST_LOCAL_FUNCTION_BIND to "bind"? > > The syntax doesn't have to be exactly as above. If someone could > take a lead on this it would be great. I don't have time for this, > I'm afraid. The Boost.LocalFunction implementation will largely rely on parameter binding techniques similar to the ones currently used by Boost.ScopeExit as suggested to me by Steven Watanable, Vicente Botet, and Alexander Nasonov. Thank you. -- Lorenzo

9 35