On 08/07/2014 01:54 PM, Marshall Clow wrote:
Release 1.56.0 of the Boost C++ Libraries is now available.
These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use.
This release contains one new library and numerous enhancements and bug fixes for existing libraries.
=== Modularization === Boost version control has migrated to a system using git submodules. This shouldn't make too much of a difference to users, although the directory structure is now a bit different.
Parts of some libraries have been moved into different modules, and several new modules have been extracted from existing code. All header paths should remain the same. The new modules are:
. Assert:Customizable assert macros. Maintained by Peter Dimov. . Core: Core utilities used by other libraries, with minimal dependencies. Maintained by Peter Dimov, Glen Fernandes and Andrey Semashev. . Lexical_Cast:General literal text conversions, such as an int represented a string, or vice-versa, from Kevlin Henney. . Throw_Exception:A common infrastructure for throwing exceptions from Boost libraries, from Emil Dotchevski. . Winapi:Windows API declarations without
, for internal Boost use. === New Libraries === . Align:Memory alignment functions, allocators, and adaptors, from Glen Fernandes. . Type_Index:Runtime/Compile time copyable type info, from Antony Polukhin.
For details, including download links, see http://www.boost.org/users/news/version_1.56.0
You can also download directly from SourceForge: http://sourceforge.net/projects/boost/files/boost/1.56.0/
To install this release on your system, see http://www.boost.org/doc/libs/release/more/getting_started/index.html
(1) I downloaded and untarred from the Unix .bz2 download. Many of the directories have 700 (user-only access) permissions, instead of the usual 755. I can correct everything by hand, but this seems like a mistake. It would be good to offer us a useful chmod command to fix this. (2) I started to look at the getting_started docs, because I expected some advice with respect to the new library structure. However, the docs all refer to 1.55.0, so I doubt that I will learn anything from them. I can muddle on without help, but I was hoping to avoid unnecessary delays in installing 1.56.0. -- Dick Hadsell 203-992-6320 Fax: 203-992-6001 Reply-to: hadsell@blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 1 American Lane, Greenwich, CT 06831-2560