October 2013 - Boost - lists.preview.boost.org

[config] Macro for unused declarations
by Jeremiah Willcock 21 Oct '13

21 Oct '13

Would it be possible to have a macro for __attribute__((unused)) and similar pragmas to portably avoid "unused typedef" and related warnings (especially from recent versions of GCC)? I have mostly removed those in Boost.Graph, but there are some that need to remain---creating a typedef to a member type of a class to make sure that the member exists, for example. Thank you. -- Jeremiah Willcock

3 2

When Boost modularization and Git migration coupling were accepted on this ML?
by Vicente J. Botet Escriba 21 Oct '13

21 Oct '13

Hi, I would not take the time to inspect all the post relating to this subject. There are a lot of post related to the subject, a lot of discussion, but what I'm locking for is a decision. So please don't replay to this post by telling me, you have just to use this tool or this other tool to have the answer. If you consider that this post is bicksheding or a bad post, please, just ignore it. I remember a post that deceded to move to Git long time ago. I would just know if (and when) the Boost community has decided to couple the move to Git and the Boost modularization. And i would like to know also if changes to the trunk repository without requesting authors permission were allowed on this move. Who accepted the plan described by S. Kelly ? Who gave him the right to update the whole Boost repository? Was this discussed on this ML or on a specific ML that is not an official Boost ML? Le 18/10/13 00:24, Stephen Kelly a écrit : > my plan for modularizing and modernizing Boost was roughly this: > > * Phase 0 - remove dead weight by bumping compiler feature requirements > * Phase 1 - move some files around so that the modularized repos form a > mostly directed graph > * Phase 2 - Form some kind of 'boost core library' or 'boost feature > normalization library' from the guts of existing libraries like > type_traits, static_assert, config mpl and utilities. > * Phase 3 - Try to port the mpl to variadic templates so that the > dependency on Boost.PP is not needed when variadic templates are available. Apologies if this is clear for most of you. IMHO, this kind of decisions should be posted with an explicit title. Best, Vicente

3 2

C++Now 2014: Call for Submissions
by Hartmut Kaiser 20 Oct '13

20 Oct '13

============================================== C++ Now Conference 2014 Aspen CO, USA, May 12-17, 2014, www.cppnow.org ============================================== Call for Submissions -------------------- We invite you to submit session proposals to the 2nd annual C++ Now Conference (Aspen CO, USA, May 12-17, 2014). Building upon the resounding success of C++ Now 2013 and five years of BoostCon, C++ Now 2014 will present leading speakers from the whole C++ community. The C++ Now Conference is dedicated to discussion and education about C++, an open and free language and standard. Our Conference will focus on discussion and education about open source software usage and developments in the C++ developer and user community. To reflect the breadth of the C++ and Boost communities, the conference includes sessions aimed at three constituencies: C++ and Boost end-users, hard-core Boost library and tool developers, and researchers pushing the boundaries of computation. The program fosters interaction and engagement within and across those groups, with an emphasis on hands-on, participatory sessions. As a multi-paradigm language, C++ is a melting pot where the most compelling ideas from other programming communities are blended in powerful ways. Historically, some of the most popular sessions at C++ Now have highlighted these concepts, from DSLs to functional programming to transactional memory and more. Bring your C#, Python, Ruby or Haskell influences to bear in an environment that will broaden their exposure. At C++ Now 2014 we would like to focus on the now established C++11 standard and the new, upcoming C++14 and how those standard are and will shape C++'s future. However, by no means this is intended to restrict the topics of proposals we hope to see. Any other topic related to C++ as outlined below is perfectly fine for submission. Important dates --------------- New proposal submissions due: December 8th, 2013. Proposals decisions sent (tentative program available): January 30th, 2014. Fully scheduled program available: February 24th, 2014. Best Presentation Awards ------------------------ We know how much effort it takes to prepare talks for our conference. For this reason we will award the best presentations in the following categories: Best Presentation, Best Short Presentation, Best Tutorial, and Best Workshop. The awards will be given based on the audience's voting. Each award will include the author's name listed on the cover of the C++ Now website for that year and a plaque containing all the C++ Now conference information. Session topics -------------- Topics of interest include, but are not restricted to, the following: * C++11/14 and how it changes life for users and library writers * General tutorial sessions on C++11/14, the C++11/14 Standards library, and one or more Boost libraries * Parallelism in the new C++11/14 standard * Parallel, distributed and GPGPU topics relating to C++ * In-depth sessions on using specific Boost libraries * Case studies on using Boost * Experts panels * Advanced sessions on implementation techniques used within Boost libraries * 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 * Software development tools and their application to C++ and or Boost * Other topics likely to be of great interest to C++ users and developers Interactive and collaborative sessions are encouraged, as this is 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 C++11 or C++14, Boost and users. Panels Panels feature three or four people presenting their ideas and experiences relating to C++11 or C++14 and 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 skills relevant to C++11 or C++14 and Boost. 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 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 should be made through the EasyChair conference management system: http://www.easychair.org/conferences/?conf=cppnow2014. 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 C++ Now website and will be available to attendees. For general information on the C++ Now 2014 paper submission or the scope of technical papers solicited; please refer to the conference website at www.cppnow.org. For any other questions about the submission process or paper format, please contact the Program Committee at cppnow2014(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 C++ Now. Hartmut Kaiser, email: hartmut.kaiser(a)gmail.com (Program Committee Chair) Joel Falcou, email: joel.falcou(a)lri.fr (Program Committee Chair) Jon Kalb, email: dave(a)boostpro.com (Conference Chair) On behalf of the conference organizers

1 0

[modularization] Trying it out doesn't quite work?
by John Maddock 20 Oct '13

20 Oct '13

OK I'm following https://svn.boost.org/trac/boost/wiki/TryModBoost Git clone proceeds OK, and I seem to have everything I should have, likewise bootstrapping b2 proceeds OK. But: b2 headers does nothing at all. Trying: b2 --with-regex results in all the expected compile errors 'cos the headers aren't found. What gives? Thanks, John. PS this is on Windows Vista.

2 1

[modularization] What do we do with "glue" headers?
by John Maddock 20 Oct '13

20 Oct '13

Trying to get this discussion somewhat back on track... There are many libraries in Boost that have "glue" headers: by this I mean small headers that allow library A to interoperate with library B. Often these are simply specializations of traits classes or function overloads, are relatively trivial, and are not included unless you need them to be. By this I mean that: suppose library B wants to interoperate with lib A. It defines a special header which #includes what it needs from lib A and defines whatever specializations are required to get the two libraries working together. Now here's the thing: there is no dependency from lib B to lib A *unless you are already using both libraries*. A good example would be the serialization lib: a simple dependency tracker would show this up as a dependency to a large part of Boost, but in fact that's not true: in the vast majority of those cases there is no such dependency unless you actually want to use both libraries together and do so by including the "glue" header. So where does the glue header belong? In most cases if you want B to interoperate with A then you define a header which: * Includes headers from both libraries. * Uses the public interface of A, but may access the internals of B (think serialization). Which would imply that the header belongs with B. Pure and simple. Except it's not, because these two libraries may be peers, and interoperability may be more complex than simply unidirectional. I don't have an answer here, but it seems to me that "dependency" is a more complex thing than simply what-includes-what (and that's without getting into header file, vs source file, vs test file dependencies). Cheers, John.

9 15

[multi_index] problems with initializer lists in Intel 14.0 for Linux
by Joaquin M Lopez Munoz 20 Oct '13

20 Oct '13

Hi, I'm having here the same problems as described for Visual Studio 2013, only in an amplified way: http://tinyurl.com/pclssoe http://tinyurl.com/nzwzpu6 Any clue much appreciated. Joaquín M López Muñoz Telefónica Digital

1 0

[multi_index] problems with initializer lists in Visual Studio 2013
by Joaquin M Lopez Munoz 20 Oct '13

20 Oct '13

I think this is related to the similar problem just discussed in connection with Boost.Unordered with the same compiler. The following struct employee { employee(int id_,std::string name_,int age_,int ssn_); // ... }; employee_set es8({{0,"Rose",40,4512},{1,"Mary",38,3345}, {2,"Jo",25,7102}}); gives me (see http://tinyurl.com/pg4fsln ) ..\libs\multi_index\test\test_copy_assignment.cpp(159) : error C2440: 'initializing' : cannot convert from 'initializer-list' to 'boost::multi_index::multi_index_container<[...]>' No constructor could take the source type, or constructor overload resolution was ambiguous and this es9={{0,"Rose",40,4512},{1,"Mary",38,3345},{2,"Jo",25,7102}, {0,"Rose",40,4512}}; results in ..\libs\multi_index\test\test_copy_assignment.cpp(162) : error C2593: 'operator =' is ambiguous D:\teeks99-10\boost\boost/multi_index_container.hpp(329): could be 'boost::multi_index::multi_index_container<[...]> &boost::multi_index::multi_index_container<[...]>::operator= (std::initializer_list<employee>)' D:\teeks99-10\boost\boost/multi_index_container.hpp(321): or 'boost::multi_index::multi_index_container<[...]> &boost::multi_index::multi_index_container<[...]>::operator = (boost::multi_index::multi_index_container<[...]> &&)' D:\teeks99-10\boost\boost/multi_index_container.hpp(313): or 'boost::multi_index::multi_index_container<[...]> &boost::multi_index::multi_index_container<[...]>::operator = (const boost::multi_index::multi_index_container<[...]> &)' while trying to match the argument list '(employee_set, initializer-list)' Is this the compiler's fault or mine? Any applicable library-side workarond? Thank you, Joaquín M López Muñoz Telefónica Digital

1 0

Password Reminder Troubles
by Olaf van der Spek 19 Oct '13

19 Oct '13

Hi, The mailing list password reminder doesn't seem to work for me @ olafvdspek(a)gmail.com and ml(a)vdspek.org. Is there a known issue (sending mail to gmail)? Olaf

2 2

[Serialization] How to retrieve a class version in an archive without loading?
by nico 18 Oct '13

18 Oct '13

Hello. My question is about program rollback and the management of archive compatibility : let's say I saved on object of type T with my program in version 1.35 => archive.txt. If I roll back my program to a previous version (let say 1.30), I'd like to check (without trying to deserialize for performance issue) if T in 1.30 has the same "BOOST_CLASS_VERSION" as the object saved in archive.txt. *In brief : is there a way to retrieve the BOOST_CLASS_VERSION of T stored in the archive ?* I read boost code, but I didn't find a "quite direct" way to do that. It seems I must get cobject_id_vector of basic_iarchive_impl, but all this stuff is private. Is their another non-intrusive way to do it ? (By non-intrusive I mean : only using the boost public stuff, or at least with a simple inheritance to get protected member of base classes?). Thanks in advance. nicolas.

2 1

Re: [boost] Boost Serialization on Sun Solaris with rwtools7_std
by Brian Wood 18 Oct '13

18 Oct '13

From: Duc Tran: > That's not all errors, still have many. > Unfortunately, my company is unable to sponsor it. I have to do it myself. > Do you have any suggestions? I have alternative serialization approach. Unlike traditional library approach most of the code only runs on one platform as an on line code generator. I believe this makes porting to other platforms simpler than traditional approach. I'm willing to port my software to Solaris if you are interested. It should be easy. It would be nice to have someone to ask about Solaris install/admin questions. Additionally I'm willing to donate 15 hours/week for six months on a project that uses my software. -- Brian Ebenezer Enterprises http://webEbenezer.net

2 1