- Boost - lists.boost.org

Boostcon 2009 call for sessions
by dan marsden 11 Nov '08

11 Nov '08

3rd annual Boost Conference 2009 Aspen CO, USA, May 3-9, 2009, www.boostcon.com ---------------------------------------------------------------------------- Call for participation ---------------------- Promising to be the main face-to-face event for all things Boost (www.boost.org) BoostCon'09 opens the door to your C++ future. 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 from TR1 to TR2 and the new C++0x 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 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 * TR1 and TR2 * 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 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 lightning-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=boostcon09. 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 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 papers 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 CD handed out to attendees. For general information on the BoostCon 2009 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 boostcon09(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 --------------- Proposals for submissions due: January 10th 2009. Proposals acceptances sent (tentative program available): February 10th, 2009 Fully scheduled program available: March 1st, 2009 Session materials due: April 1st 2009. 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

4 7

[thread] condition::try_wait() and thread::try_join()?
by vicente.botet 11 Nov '08

11 Nov '08

Hi Anthony, I'm sure there you have a good rationale to don't have condition::try_wait() or thread::try_join() functions. Could you share with us? Can these functions be emulated? If yes, why not adding them? Best, Vicente

3 7

Re: [boost] Getting started build section
by raindog＠macrohmasheen.com 11 Nov '08

11 Nov '08

That would be great if build told you where it placed filed :) ------Original Message------ From: David Abrahams Sender: boost-bounces(a)lists.boost.org To: boost(a)lists.boost.org ReplyTo: boost(a)lists.boost.org Sent: Nov 10, 2008 11:46 PM Subject: Re: [boost] Getting started build section on Thu Nov 06 2008, Steven Watanabe <watanabesj-AT-gmail.com> wrote: > AMDG > > David Abrahams wrote: >> --stagedir and --build-dir are very similar. We should probably make the >> same decision about documenting both of them. >> > > How similar are they really? > > build-dir primarily controls where all the intermediate files go. > stagedir controls where the libraries get installed to. > I would expect anyone who uses stage to care about where > the libraries end up, even if the default is fine. Okay, point taken. If there's going to be a default at all, I suppose Boost.Build should end by printing a message telling you where they've been installed... and probably begin by printing a message telling you where they *will* be instlaled. -- Dave Abrahams BoostPro Computing http://www.boostpro.com _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost Sent from my Verizon Wireless BlackBerry

1 0

Getting started build section
by Vladimir Prus 11 Nov '08

11 Nov '08

Dave, I am reading the getting started guide, and think some of the build instructions can be improved. I can do this myself, if we agree on the nature of the changes. For reference, I'm looking at: http://www.boost.org/doc/libs/1_37_0/more/getting_started/windows.html 5 Prepare to Use a Boost Library Binary I think the section title is too long-winded. "Prepare" does not even suggest any kind of building. And of course, we have many libraries, so saying "a ... Binary" is not accurate. Would "Building Library Binaries" be more to the point? The installers supplied by BoostPro Computing will download and install pre-compiled binaries into the lib\ subdirectory of the boost root, typically C:\Program Files\boost\boost_1_37_0\lib\. If you installed all variants of the Boost.Regex binary, you're done with this step. Otherwise, please run the installer again and install them now. I can't understand what the second sentence say. If installer allows to install only some variants of Boost.Regex, then documentation should to request the user to run the installer again, and install the remaining ones. I can't fix this text without knowing what it means. 5.2 Or, Build Binaries From Source If you're using an earlier version of Visual C++, or a compiler from another vendor, you'll need to use Boost.Build to create your own binaries. Earlier than what? No version of Visual C++ is mentioned in the preceding text. Boost.Build is a text-based system for developing, testing, and installing software. To use it, you'll need an executable called bjam. 5.2.1 Get bjam bjam is the command-line tool that drives the Boost Build system. To build Boost binaries, you'll invoke bjam from the Boost root. The last sentence of 5.2 and the first sentence of 5.2.1 essentially duplicate each other. Besides, bjam does not really drives Boost.Build (just like my car does not drive me, usually). First, find the toolset corresponding to your compiler in the following table. The kylix should be removed from the table. "FreeScale" should be "Freescale". This should also link to the list of toolchains in Boost.Build docs. 5.2.3 Select a Build Directory Boost.Build will place all intermediate files it generates while building into the build directory. If your Boost root directory is writable, this step isn't strictly necessary: by default Boost.Build will create a bin.v2/ subdirectory for that purpose in your current working directory. I suggest that this section be dropped. In describes a non-mainstream usage that is better be describe elsewhere. FWIW, the case of building source straight from CD does not seem reasonable, since with large number of headers the performance will be horrible. Likewise, building from a network drive is not a good idea. So, copying source to a local drive and building from there is the best thing. bjam --build-dir=build-directory --toolset=toolset-name --build-type=complete stage Per above, I suggest we drop --build-dir. --toolset= should become toolset= This section should also link to Boost.Build doc section about command line syntax. 5.3 Expected Build Output This section fails to mention the single most important point -- that the libraries are produced, and where they are produced. In fact, I don't see an obvious purpose of this section to the user -- it just says "oh, and those kinds of message appear". This section fails to explain what is produced as result -- like that libraries will be placed in the 'stage' directory. I'd suggest rewording the section like this: 5.3 Interpreting the results. The build process produces a large number of output during compilation, including diagnostic messages from Boost.Build, names of files being compiled and messages from the compiler. A summary is printed at the end. If the summary does not include any failed targets, your build is successful, and the library binaries can be found in the 'stage' directory. Otherwise, you can browse the output to see which libraries failed to build, and which compile errors were produced. You can also run bjam again, with the same option, to try compiling the failed files again. A the beginning of the build, you will be informed what functionality of C++ Boost libraries is disabled because of lack of required third party libraries. You might want to check that you don't require the disabled functionality, and perform additional configuration (see individual libraries documentation). If it seems like the build system can't find your compiler and/or linker, consider setting up a user-config.jam file as described in the Boost.Build documentation. This should have a link to Boost.Build section about configuration, not to the top-level docs. Comments? - Volodya

4 9

Group libraries by topic in the documentation
by Kevin Sopp 11 Nov '08

11 Nov '08

There are 92 entries in the library overview now (http://www.boost.org/doc/libs) I believe this is quite intimidating for a new user. I have come up with a scheme of grouping things (I don't claim it is perfect and I put libraries that I wasn't sure about into "Others"). Each library should only appear once even if that one category doesn't describe the library's purpose perfectly. The "Others" section could be subdivided further, i.e. Concurrency and Time categories come to mind but I didn't deem that necessary. Additionally, it would be nice to 1) indicate header-only status via a preceding (+) symbol and a library-only status via (-). This can be combined into (+/-) for libraries that support both. 2) indicate deprecated library status via "deprecated, use XXX instead". 3) indicate expected learning curve via color (green, yellow, red) where red is intended for something like Proto and green for Any. Yellow could be used for a library like Program Options. Containers----------------------- Any Array Bimap Circular Buffer Dynamic Bitset Intrusive Multi-Array Multi-Index Pointer Container Tuple Unordered Variant Functional Programming----------- Bind Functional Lambda Member Function I/O------------------------------ Filesystem Format IO State Savers Iostreams Serialization Math----------------------------- Accumulators Disjoint Sets Interval Math Math Common Factor Math Octonion Math Quaternion Math/Special Functions Math/Statistical Distributions Random Rational uBLAS Memory Management---------------- Pool Smart Ptr Metaprogramming------------------ Call Traits Compressed Pair Concept Check Enable If Function Types Fusion MPL Operators Parameter Preprocessor Property Map Proto Statechart Static Assert Type Traits Typeof Networking----------------------- Asio Text processing------------------ Regex Spirit String Algo Tokenizer Xpressive Others--------------------------- Assign CRC Conversion Date Time Exception Foreach Function Functional/Hash GIL Graph In Place Factory, Typed In Place Factory Interprocess Iterators Min-Max MPI Numeric Conversion Optional Program Options Python Range Ref Signals System Test TR1 Thread Timer Units Utility Value Initialized Tribool Wave Boost Internal------------------- Compatibility Config Integer

5 5

[Website] Navigation and discoverability
by David Abrahams 11 Nov '08

11 Nov '08

Hi all, I still have a hard time finding my way around the website since it was restructured. I'm having at least two problems: 1. I can pretty much guarantee that manually changing a URL in the address bar of my browser will fail, I think because the URLs are deep and relatively unforgiving. Unfortunately I have little or no insight into what would fix this problem. 2. Many files have version numbers in their URLs, and there doesn't seem to be any way to link to "whatever the latest is." Also, once we have that shouldn't we try to encourage search engines to prioritize that URL as opposed to any of the many near-duplicates (not that I know how)? 3. I can't get a good feeling for what's on the site and how it's structured without hopping around all over the place. For example, if I'm looking for mailing lists, do I want "community" or "support?" The answer isn't immediately obvious. http://www.boostpro.com has drop-down menus that are entirely done with highly portable CSS; I got the base code from http://www.cssplay.co.uk/menus/final_drop.html. Something like that would be an immense help in finding what I'm looking for. Thoughts? -- Dave Abrahams BoostPro Computing http://www.boostpro.com

3 2

BOOST_MATH_NO_LONG_DOUBLE_MATH_FUNCTIONS causes build to fail
by Steve M. Robbins 11 Nov '08

11 Nov '08

Hi, If the symbol BOOST_MATH_NO_LONG_DOUBLE_MATH_FUNCTIONS is defined (see <boost/math/tools/config.hpp>) then the build fails [1] as follows: libs/math/build/has_long_double_support.cpp:9:2: error: #error "long double support is not supported by Boost.Math on this Plaform: the long double version of the TR1 library will not be built." ...failed gcc.compile.c++ bin.v2/libs/math/build/has_long_double_support.test/gcc-4.3.2/release/debug-symbols-on/link-static/has_long_double_support.o... and several others, ending with: ...failed updating 8 targets... ...skipped 368 targets... ...updated 2074 targets... make: *** [build-stamp] Error 1 The failure is caused by an #error directive in has_long_double_support.cpp, suggesting this behaviour is deliberate. How can this be made to be non-fatal? Thanks, -Steve P.S. The behaviour is easy to reproduce: just stick #define BOOST_MATH_NO_LONG_DOUBLE_MATH_FUNCTIONS into config.hpp. [1] http://buildd.debian.org/fetch.cgi?&pkg=boost1.36&ver=1.36.0-3&arch=hppa&st…

1 0

[threadpool] new version - fork/join (recursive/fibers)
by k-oli＠gmx.de 11 Nov '08

11 Nov '08

Hello, v13: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=boost-… after the discussion yesterday I've modified the code. Now the pool can be configured (second template argument of tp::pool) to use recursive invokation of tasks or fibers in order to enable fork/join semantics. I've found that the recursive invokation is more than two times faster than using fibers (see examples recursive_fibonacci_recursive_task.cpp and recursive_fibonacci_with_fibers.cpp). The code using fibers sometimes raises an assertion in ~mutex() (used in work-stealing queue). For this reason and following the discussions I think I'll remove the support for fibers from threadpool. regards, OPliver

6 24

[signals2][review] The review period of the signals2 library is over
by Stjepan Rajko 11 Nov '08

11 Nov '08

Hello all, The review period of the signals2 library finishes today, November 10th. I would like to thank the author, Frank Mori Hess, for preparing the library for review and for diligently answering questions, and all those that have participated in the review for their thoughtful comments and reviews. A few more reviews will be coming late - if anyone that hasn't contacted me yet would like to submit a review in the following few days please let me know so I know to wait for your review. I will start working on summarizing the content of the reviews and comments submitted so far, and will post a report within a week. Kind regards, Stjepan

1 0

[chrono] Help need for Linux implementation
by Beman Dawes 11 Nov '08

11 Nov '08

I've got a boostified version of the C++0x <chrono> header working on Windows, but need help for the Linux implementation. I wrote a test program (see below). It compiles OK but gets a link failure: /tmp/ccmT80bD.o: In function `clk()': test.cpp:(.text+0x192): undefined reference to `clock_gettime' collect2: ld returned 1 exit status What am I doing wrong? The command I'm using is simply "g++ test.cpp". Ubuntu 8.04 with all updates applied. Thanks, --Beman ------------------------------- #include <time.h> #include <stdlib.h> #include <errno.h> #include <iostream> unsigned long long clk() { timespec ts; if ( clock_gettime( CLOCK_MONOTONIC, &ts ) ) { std::cout << "errno " << errno << "\n"; exit(0); } return (unsigned long long)ts.tv_sec * 1000000000 + ts.tv_nsec; } int main() { std::cout << clk() << " nanoseconds\n"; return 0; }

2 2