- Boost - lists.boost.org

Requesting svn access
by Mathias Gaunard 14 Oct '13

14 Oct '13

Hi, There are a couple of warnings generated by unmaintained libraries that I'd like to fix. (In particular https://svn.boost.org/trac/boost/ticket/9115) Would it be possible to have write access so that I can commit these to trunk and then to release?

3 2

[config] Patch for clang.hpp to support clang in Windows using VC++ RTL
by Edward Diener 14 Oct '13

14 Oct '13

Once Boost 1.55 is out the doors can I apply the attached patch for clang when _MSC_VER is defined ? Unfortunately clang in this situation does not currently support the C++11 types char16_t or char32_t ( there is a bug report for this ), and this means trying to compile Boost libraries like type_traits without this patch yields many errors. I would have used the BOOST_WORKAROUND macro but clang does not support a value which gives a single number for the compiler version so I felt that drumming up multiple BOOST_WORKAROUNDs using major/minor/patch version numbers was too much of a hack to bother about.

2 3

Support for BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION
by Joaquin M Lopez Munoz 14 Oct '13

14 Oct '13

I understand there's been some discussion about dropping support for compliers with BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION defined. Has some final decision been made about this? Thank you, Joaquín M López Muñoz Telefónica Digital

6 23

[algorithm][array] Inspection report (tabs)
by Michel Morin 14 Oct '13

14 Oct '13

Hi Marshall, An inspection report says that some files contain tabs: ( http://boost.cowic.de/rc/docs-inspect-trunk.html ) algorithm boost/algorithm/cxx14/equal.hpp: *Tab* boost/algorithm/cxx14/mismatch.hpp: *Tab* libs/algorithm/string/doc/external_concepts.html: Unlinked file libs/algorithm/string/test/find_test.cpp: *Tab* libs/algorithm/string/test/split_test.cpp: *Tab* libs/algorithm/test/iterator_test.hpp: *C*, *Lic*, *Tab* array libs/array/doc/Jamfile.v2: *C*, *Lic* libs/array/test/array_constexpr.cpp: *Tab* libs/array/test/array_getfail1.cpp: *Tab* Regards, Michel

1 0

Permission to proceed?
by Stephen Kelly 14 Oct '13

14 Oct '13

Hello, Now that the beta has been out for a while, I'd like to proceed with my clean-up commits in trunk. I'd like to commit the patch in http://thread.gmane.org/gmane.comp.lib.boost.devel/244392/focus=244397 immediately and then proceed to remove the resulting dead code. Can I go ahead and do that? I assume that does not have any effect on the release branch. Thanks, Steve.

6 13

Re: [boost] Improving Documentation
by Andrew Hundt 14 Oct '13

14 Oct '13

On Fri, Oct 11, 2013 at 2:49 PM, Robert Ramey <ramey(a)rrsd.com> wrote: > Mathias Gaunard wrote: > > On 11/10/13 15:31, TONGARI J wrote: > > > >> I think Doxygen is fine for "regular" libraries, but I always have a > >> question: how could a library like Spirit be doucumented with it? > > > > Same as any other library. > > You document the data types and the functions. > > what about the type constraints - aka concepts? > and templates? You can document template parameters with doxygen. If you are using the boost concept check library you can also use those classes to document your concepts. I believe gil does that if you would like an example. You can also always add custom fields fairly easily if none of the existing ones meet you needs. Cheers! Andrew Hundt

5 5

[config][release] Release notes for old compilers.
by Daniel James 14 Oct '13

14 Oct '13

Hi, I added a little release notes for config, and also a note about removing support for older compilers in the future. If this concerns you, please give it a quick check and let me know if you want any changes. This release note is not a promise that future changes will or won't be made, and it can be changed if appropriate. Sorry that this is a bit late. We can still change the release notes after the beta (and final) release, so don't worry about that. thanks, Daniel

5 12

Review request: Require a SFINAE capable compiler
by Stephen Kelly 14 Oct '13

14 Oct '13

Hello, Several of the ancient compilers define BOOST_NO_SFINAE. The attached patch removes support for those versions of the compilers which are not capable of SFINAE. This bumps the compiler requirement to remove support for Borland 5.x, Metrowerks prior to 9.0, and SunPro prior to 5.7. Compilers based on EDG 238 are also affected, though it is unknown what those are. Ok to commit? Thanks, Steve.

6 12

[compiler workaround] Are we purging history?
by Daryle Walker 14 Oct '13

14 Oct '13

As I understand it, the people modernizing Boost code by getting rid of old compiler workarounds are doing two things: 1. Remove the workaround macro flags and the code that uses them, leaving the code that doesn't use the workarounds behind. 2. Purging those workaround macros from Boost.Config. If we are doing [2], why? Doing [1] is sufficient for modernization. Doing [2] is just purging history that we spent blood/sweat/tears generating. Authors/maintainers generally have free reign to use as many or as few workarounds as they want. They can't do that if we're deleting that knowledge from Boost.Config. Daryle W.

3 2

Re: [boost] Improving Documentation
by Andrew Hundt 14 Oct '13

14 Oct '13

On Thu, Oct 10, 2013 at 4:29 PM, Mathias Gaunard < mathias.gaunard(a)ens-lyon.org> wrote: > > Documentation like this is generated by preprocessing Doxygen XML output > to integrate it into Boostbook and have a good look for C++ references. > It has most of what you can expect from Doxygen + the Boostbook stuff > which gives better cross-referencing than simple Doxygen. > > I personally don't understand how one cannot notice that the blue bits > that become underlined when you hover them and change colors once visited > are hyperlinks (especially since that's also true for any other hyperlink > in Boost docs and most of the World Wide Web). > What do you suggest would be better? I believe part of the problem is that everything is blue. For instance, on the boost.lockfree page: http://www.boost.org/doc/libs/1_54_0/doc/html/lockfree/reference.html#heade… - The following words are blue: - namespace, template, bool, struct, capacity, template, typename, allocator, class, fixed_sized, queue, spec_queue, stack - Out of those, the following are links: - fixed_sized, capacity, allocator, queue, spec_queue, stack I believe there is a word to describe the concept of building things such that people expect to interact with them. I think it is called an affordance, so a link should "afford" clicking. https://en.wikipedia.org/wiki/Affordance When it is your first time ever on the site, even if you try to hover over one of the blue words, you may choose one that can't be clicked on, then assume the same applies for the others. IMHO, changing the color of links or making the underlines always visible could be helpful. One possible improvement would be what Mario Mulansky described. In the Table of Contents of libraries the Reference section could contain a list of links to headers, classes, functions, metafunctions, and definitions. Then if you click to the reference link where it currently just lists headers it could also provide the synopsis of the aforementioned items and links to the detailed docs. Right now all of the documentation is an extremely deep hierarchical structure, which if I recall my conventions correctly has been moved away from in modern user experience design. Most websites try to focus on getting you to the information you need in as few clicks as possible. That is why I mentioned cppreference.com in my previous email, if you check out that site nearly everything is 3 levels deep or less. Since boost is so much larger a total of 4 levels with the top one being the list of libraries would make sense. Some link to the libs unit test and/or example folders in each library would also be helpful. These are a couple small, concrete steps that would probably help with browsing but aren't too out there. It doesn't help some of the possibilities for improved text which could also benefit, but it does help many things at a high level. As a side note, I wonder if the boost main page could be better served as a wiki of some sort? Cheers! Andrew Hundt

3 2