- Boost - lists.boost.org

Re: [boost] [Boost-commit] svn:boost r78273 - in trunk: boost/filesystem libs/filesystem/test libs/filesystem/test/msvc10 libs/filesystem/test/msvc10/macro_default_test
by Steven Watanabe 01 May '12

01 May '12

AMDG This broke the regression tests: error: Unable to find file or target named error: 'macro_default_test.cpp' error: referred from project at error: '../libs/filesystem/test' In Christ, Steven Watanabe On 04/30/2012 08:00 AM, bdawes(a)acm.org wrote: > Author: bemandawes > Date: 2012-04-30 11:00:21 EDT (Mon, 30 Apr 2012) > New Revision: 78273 > URL: http://svn.boost.org/trac/boost/changeset/78273 > > Log: > Revert to BOOST_FILESYSTEM_STATIC_LINK as the default if no linkage macros supplied. See http://www.boost.org/doc/libs/1_49_0/libs/config/doc/html/boost_config/boos… > Add test to verify correct default. > Added: > trunk/libs/filesystem/test/msvc10/macro_default_test/ > trunk/libs/filesystem/test/msvc10/macro_default_test/macro_default_test.vcxproj (contents, props changed) > Text files modified: > trunk/boost/filesystem/config.hpp | 2 +- > trunk/libs/filesystem/test/Jamfile.v2 | 1 + > trunk/libs/filesystem/test/msvc10/filesystem-v3.sln | 10 ++++++++++ > 3 files changed, 12 insertions(+), 1 deletions(-) > > Modified: trunk/boost/filesystem/config.hpp > ============================================================================== > --- trunk/boost/filesystem/config.hpp (original) > +++ trunk/boost/filesystem/config.hpp 2012-04-30 11:00:21 EDT (Mon, 30 Apr 2012) > @@ -56,7 +56,7 @@ > > #if !defined(BOOST_FILESYSTEM_DYN_LINK) && !defined(BOOST_FILESYSTEM_STATIC_LINK) \ > && !defined(BOOST_ALL_DYN_LINK) && !defined(BOOST_ALL_STATIC_LINK) > -# define BOOST_FILESYSTEM_DYN_LINK > +# define BOOST_FILESYSTEM_STATIC_LINK > #endif > > #if defined(BOOST_ALL_DYN_LINK) && !defined(BOOST_FILESYSTEM_DYN_LINK) > > Modified: trunk/libs/filesystem/test/Jamfile.v2 > ============================================================================== > --- trunk/libs/filesystem/test/Jamfile.v2 (original) > +++ trunk/libs/filesystem/test/Jamfile.v2 2012-04-30 11:00:21 EDT (Mon, 30 Apr 2012) > @@ -17,6 +17,7 @@ > > test-suite "filesystem" : > [ run convenience_test.cpp ] > + [ compile macro_default_test.cpp ] > [ run deprecated_test.cpp ] > [ run fstream_test.cpp ] > [ run large_file_support_test.cpp ] > > Modified: trunk/libs/filesystem/test/msvc10/filesystem-v3.sln > ============================================================================== > --- trunk/libs/filesystem/test/msvc10/filesystem-v3.sln (original) > +++ trunk/libs/filesystem/test/msvc10/filesystem-v3.sln 2012-04-30 11:00:21 EDT (Mon, 30 Apr 2012) > @@ -106,6 +106,12 @@ > EndProject > Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "exec_monitor_lib", "exec_monitor_lib\exec_monitor_lib.vcxproj", "{272DFC15-6292-49DF-B457-6784A183EAC3}" > EndProject > +Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "macro_default_test", "macro_default_test\macro_default_test.vcxproj", "{36E2032D-F9E6-4FBA-9630-3D4AC518DC6C}" > + ProjectSection(ProjectDependencies) = postProject > + {3640605D-6F82-493D-879F-8F30762DA554} = {3640605D-6F82-493D-879F-8F30762DA554} > + {2C1770A4-4AC3-4102-9D36-E652DBB686D8} = {2C1770A4-4AC3-4102-9D36-E652DBB686D8} > + EndProjectSection > +EndProject > Global > GlobalSection(SolutionConfigurationPlatforms) = preSolution > Debug|Win32 = Debug|Win32 > @@ -228,6 +234,10 @@ > {272DFC15-6292-49DF-B457-6784A183EAC3}.Debug|Win32.Build.0 = Debug|Win32 > {272DFC15-6292-49DF-B457-6784A183EAC3}.Release|Win32.ActiveCfg = Release|Win32 > {272DFC15-6292-49DF-B457-6784A183EAC3}.Release|Win32.Build.0 = Release|Win32 > + {36E2032D-F9E6-4FBA-9630-3D4AC518DC6C}.Debug|Win32.ActiveCfg = Debug|Win32 > + {36E2032D-F9E6-4FBA-9630-3D4AC518DC6C}.Debug|Win32.Build.0 = Debug|Win32 > + {36E2032D-F9E6-4FBA-9630-3D4AC518DC6C}.Release|Win32.ActiveCfg = Release|Win32 > + {36E2032D-F9E6-4FBA-9630-3D4AC518DC6C}.Release|Win32.Build.0 = Release|Win32 > EndGlobalSection > GlobalSection(SolutionProperties) = preSolution > HideSolutionNode = FALSE > > Added: trunk/libs/filesystem/test/msvc10/macro_default_test/macro_default_test.vcxproj > ============================================================================== > --- (empty file) > +++ trunk/libs/filesystem/test/msvc10/macro_default_test/macro_default_test.vcxproj 2012-04-30 11:00:21 EDT (Mon, 30 Apr 2012) > @@ -0,0 +1,91 @@ > +<?xml version="1.0" encoding="utf-8"?> > +<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> > + <ItemGroup Label="ProjectConfigurations"> > + <ProjectConfiguration Include="Debug|Win32"> > + <Configuration>Debug</Configuration> > + <Platform>Win32</Platform> > + </ProjectConfiguration> > + <ProjectConfiguration Include="Release|Win32"> > + <Configuration>Release</Configuration> > + <Platform>Win32</Platform> > + </ProjectConfiguration> > + </ItemGroup> > + <PropertyGroup Label="Globals"> > + <ProjectGuid>{36E2032D-F9E6-4FBA-9630-3D4AC518DC6C}</ProjectGuid> > + <Keyword>Win32Proj</Keyword> > + <RootNamespace>macro_default_test</RootNamespace> > + </PropertyGroup> > + <Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" /> > + <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'" Label="Configuration"> > + <ConfigurationType>Application</ConfigurationType> > + <UseDebugLibraries>true</UseDebugLibraries> > + <CharacterSet>Unicode</CharacterSet> > + </PropertyGroup> > + <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'" Label="Configuration"> > + <ConfigurationType>Application</ConfigurationType> > + <UseDebugLibraries>false</UseDebugLibraries> > + <WholeProgramOptimization>true</WholeProgramOptimization> > + <CharacterSet>Unicode</CharacterSet> > + </PropertyGroup> > + <Import Project="$(VCTargetsPath)\Microsoft.Cpp.props" /> > + <ImportGroup Label="ExtensionSettings"> > + </ImportGroup> > + <ImportGroup Label="PropertySheets" Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"> > + <Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" /> > + </ImportGroup> > + <ImportGroup Label="PropertySheets" Condition="'$(Configuration)|$(Platform)'=='Release|Win32'"> > + <Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" /> > + </ImportGroup> > + <PropertyGroup Label="UserMacros" /> > + <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"> > + <LinkIncremental>true</LinkIncremental> > + </PropertyGroup> > + <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'"> > + <LinkIncremental>false</LinkIncremental> > + </PropertyGroup> > + <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"> > + <ClCompile> > + <PrecompiledHeader> > + </PrecompiledHeader> > + <WarningLevel>Level3</WarningLevel> > + <Optimization>Disabled</Optimization> > + <PreprocessorDefinitions>WIN32;_DEBUG;_CONSOLE;%(PreprocessorDefinitions)</PreprocessorDefinitions> > + <AdditionalIncludeDirectories>../../../../..</AdditionalIncludeDirectories> > + </ClCompile> > + <Link> > + <SubSystem>Console</SubSystem> > + <GenerateDebugInformation>true</GenerateDebugInformation> > + </Link> > + </ItemDefinitionGroup> > + <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'"> > + <ClCompile> > + <WarningLevel>Level3</WarningLevel> > + <PrecompiledHeader> > + </PrecompiledHeader> > + <Optimization>MaxSpeed</Optimization> > + <FunctionLevelLinking>true</FunctionLevelLinking> > + <IntrinsicFunctions>true</IntrinsicFunctions> > + <PreprocessorDefinitions>WIN32;NDEBUG;_CONSOLE;%(PreprocessorDefinitions)</PreprocessorDefinitions> > + </ClCompile> > + <Link> > + <SubSystem>Console</SubSystem> > + <GenerateDebugInformation>true</GenerateDebugInformation> > + <EnableCOMDATFolding>true</EnableCOMDATFolding> > + <OptimizeReferences>true</OptimizeReferences> > + </Link> > + </ItemDefinitionGroup> > + <ItemGroup> > + <ClCompile Include="..\..\macro_default_test.cpp" /> > + </ItemGroup> > + <ItemGroup> > + <ProjectReference Include="..\filesystem_lib\filesystem_lib.vcxproj"> > + <Project>{2c1770a4-4ac3-4102-9d36-e652dbb686d8}</Project> > + </ProjectReference> > + <ProjectReference Include="..\system_lib\system_lib.vcxproj"> > + <Project>{3640605d-6f82-493d-879f-8f30762da554}</Project> > + </ProjectReference> > + </ItemGroup> > + <Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" /> > + <ImportGroup Label="ExtensionTargets"> > + </ImportGroup> > +</Project> > \ No newline at end of file > _______________________________________________ > Boost-commit mailing list > Boost-commit(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-commit

2 1

Re: [boost] [exception] warning about non-virtual destructor - resolution?
by Hite, Christopher 30 Apr '12

30 Apr '12

This is annoying me too: boost_1_49_0/boost/checked_delete.hpp:34:5: warning: deleting object of polymorphic class type 'boost::error_info<boost::tag_original_exception_type, const std::type_info*>' which has non-virtual destructor might cause undefined behaviour [-Wdelete-non-virtual-dtor] A) easy solution /boost_1_49_0/boost/exception/detail/error_info_impl.hpp It's probably easiest to just make ~error_info_base() virtual. It doesn't cost much since there's already a virtual table. B) harder solution The other cooler C++11 alternative is declare error_info final. I tried it on gcc-4.7.0 and it works wonderfully. Since the compiler knows you can not derive a class from that type it knows a that deconstructor is complete. struct base{ virtual void foo(); }; struct derived final : base { }; //struct illegal : derived {}; // error: cannot derive from 'final' base 'derived' in derived type 'illegal' void kill(derived* d){ delete d; // no complaint } I vote for A, because you'd anyway have to detect support for final. Chris

12 48

Re: [boost] [type_traits] has_equal_to< std::vector<T> > always true_
by Frédéric Bron 30 Apr '12

30 Apr '12

> We could use <boost/detail/container_fwd.hpp> here (rather like Boost.Hash > does, which has a similar issue) and get the best of both worlds? My > concern about making it a separate header, is that it runs the risk of ADL > errors if the #includes are inconsistent across translation units. I assume > that only forward declarations are needed for the containers? This looks a very good idea. It is a pity that the standard does not provide such header as it does for iostreams (iosfwd). However, I see that <boost/detail/container_fwd.hpp> has some troubles with many compilers, in particular with g++. // GNU libstdc++ 3 // Disable forwarding for all recent versions, as the library has a // versioned namespace mode, and I don't know how to detect it. This is a major drawback but maybe we can do something for it. I see also that with the new standard, this header is now not exhaustive; we have to include all of these: * <array> - <deque> * <forward_list> - <list> - <vector> - <map> - <set> * <unordered_map> * <unordered_set> - <queue> - <stack> - <string> - <bitset> *: missing headers in <boost/detail/container_fwd.hpp> Frédéric

2 1

Exception visibility and non-GCC compilers
by Mathias Gaunard 30 Apr '12

30 Apr '12

Exceptions types need to be exported so that shared libraries work correctly. Currently, the only code I see that does this is in Boost.Exception : #if defined(__GNUC__) # if (__GNUC__ == 4 && __GNUC_MINOR__ >= 1) || (__GNUC__ > 4) # pragma GCC visibility push (default) # endif #endif ... some exception type being declared or defined #if defined(__GNUC__) # if (__GNUC__ == 4 && __GNUC_MINOR__ >= 1) || (__GNUC__ > 4) # pragma GCC visibility pop # endif #endif But shouldn't we have macros to make this work with other compilers too? I'm not sure all unix-like compilers pretend to be GCC 4.1+.

2 3

[pool] Definition of a static_pool ?
by DUPUIS Etienne 30 Apr '12

30 Apr '12

Greetings, The Boost.Pool class describes a pool of buffer, pool whose size grows as needed. This is very convenient but there usage cases where the pool should not perform any dynamic memory allocation, i.e. the maximum number of simultaneously required buffers is known at initialization. I have hence defined a simple class 'static_pool' (see below), which (i) allocate all requested buffers at initialization; (ii) fails (returns null) if more buffers are being asked for at runtime. Does such a class has its place within the Boost Pool library ? Regards, Étienne #ifndef BOOST_STATIC_POOL_HPP #define BOOST_STATIC_POOL_HPP #include <boost/pool/pool.hpp> namespace boost { template<typename UserAllocator> class static_pool : protected pool<UserAllocator> { public : // Overridden functions explicit static_pool(const size_type nrequested_size) : pool<UserAllocator>(nrequested_size, nrequested_size) { free(malloc()); } void * malloc() { return store().empty() ? NULL : store().malloc(); } public : // Inherited functions void free(void * const chunk) { return pool<UserAllocator>::free(chunk); } size_type get_requested_size() const { return pool<UserAllocator>::get_requestedSize(); } bool is_from(void * const chunk) const { return pool<UserAllocator>::is_from(chunk); } }; } #endif Ce message et toutes les pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute modification, édition, utilisation ou diffusion non autorisée est interdite. Si vous avez reçu ce message par erreur, merci de nous en avertir immédiatement. ATEME décline toute responsabilité au titre de ce message s'il a été altéré, déformé, falsifié ou encore édité ou diffusé sans autorisation. This message and any attachments are confidential and intended solely for the addressees. Any unauthorized modification, edition, use or dissemination is prohibited. If you have received this message by mistake, please notify us immediately. ATEME decline all responsibility for this message if it has been altered, deformed, falsified or even edited or disseminated without authorization. Note: To protect against computer viruses, e-mail programs may prevent sending or receiving certain types of file attachments.

7 18

[filesystem] [system] Suddenly, dynamic linking by default
by Lars Viklund 30 Apr '12

30 Apr '12

Hello list. I have a habit of tracking trunk to find out if there's any strangeness or mistakes done on the platforms I target. A while ago I encountered some strange linking errors on some of my projects, which in the end turned out to be because for some reason, Boost.Filesystem and Boost.System now attempt to be dynamically linked by default, both symbol-decoration-wise and auto-link filename-wise. I happened to have some older shared libraries from an older trunk version lying around, so they were suddenly and unexpectedly picked up instead of my fresh static libraries. Even without my library hygiene deficiencies, the decision (which I have yet to see a rationale or announcement about) will cause a lot of problems. Why is it that System/Filesystem suddenly default to dynamic linking? Are there problems about linking statically? Why are there then static libraries built at all? Is this just some personal preference of the author that goes contrary to the general approach of Boost? Such choices have _massive_ impacts on consumers of the code, they should not be made lightly and if there is a really concrete need to do so, why is it not documented and thoroughly explained? Linking dynamically requires you to deploy the Boost DLLs to the end user, which prevents any plugin-like deployment, as they tend to require a single self-contained shared library with no dependencies, which implies linking to a static language runtime of choice. Dynamic linking of Boost means that you need to share a CRT between the project and Boost, which implies that the only CRT choice is the dynamic one, which prevents many deployment scenarios, as you have to deploy _that_ as well to the end user, either as a redistributable install or as a private deployment. This also has an impact on code size, as there is no dead-code elimination possible when the code resides in a DLL, you have to ship _all_ of the library even if you use a few convenience functions. For one of my projects (an extension to a popular music player), this would inflate its size many times for each and every download, as the software is deployed as a single ZIP archive through automatic update services. Additionally, the autolink macros to force symbol decoration and linking for a static link are undocumented in the Boost.Config table [1], which explicitly states that all libraries that can be statically linked will be statically linked. There is no mention of libraries that arbitrarily decide to go dynamic, just that some libraries are only available in dynamic form. For future reference for anyone finding this in archives, the undocumented, and in this case required, macros to force a static link and symbol decoration are: BOOST_<WHATEVER>_STATIC_LINK or BOOST_ALL_STATIC_LINK [1] http://www.boost.org/doc/libs/1_49_0/libs/config/doc/html/index.html#boost_… -- Lars Viklund | zao(a)acc.umu.se

5 6

[iostream] tests broken due to dependency on removed filesystem internals
by Jürgen Hunold 30 Apr '12

30 Apr '12

Hi, almost all Boost.Iostreams test fail with: bin.v2/libs/iostreams/test/array_test.test/gcc-4.6/debug/array_test.o In file included from ../array_test.cpp:14:0: ../detail/temp_file.hpp:16:46: fatal error: boost/filesystem/v3/operations.hpp: No such file or directory compilation terminated. The v3/ was removed recently as v2 was finally dropped. Patch to fix this attached. This gets a lot of the tests running. Okay to commit? There are some remaining failures. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold(a)gmx.eu !

3 4

[multiprecision] Looking for a review manager
by John Maddock 29 Apr '12

29 Apr '12

Just a quick line to remind/hassle you all that I'm still looking for a review manager for the multiprecision library: http://svn.boost.org/svn/boost/sandbox/big_number/libs/multiprecision/doc/h… All volunteers/victims gratefully accepted ;-) Many thanks in advance, John.

1 0

Re: [boost] Slow Bugs Tracker
by Olaf van der Spek 29 Apr '12

29 Apr '12

Hi, A few months ago there seemed to be plans to improve Trac. What's the status of those plans? Trac is still slow as hell. http://lists.boost.org/Archives/boost/2011/12/188639.php http://lists.boost.org/Archives/boost/2011/12/188937.php -- Olaf

7 44

[utility] convention inconsistencies
by lcaminiti 29 Apr '12

29 Apr '12

Hello all, I'm adding IdentityType to Boost.Utility and I have a couple of question about conventions: 1) Is there a reason why utility.hpp does not include all headers in boost/utility/? 2) Is there a reason why in the Documentation the utility sub-libraries are not named Boost.Utility/EnableIf bust just Boost.EnableIf? http://www.boost.org/doc/libs/1_49_0/ In boost/utility/ directory: addressof.hpp base_from_member.hpp binary.hpp compare_pointees.hpp declval.hpp enable_if.hpp identity_type.hpp in_place_factory.hpp result_of.hpp swap.hpp typed_in_place_factory.hpp value_init.hpp But boost/utility.hpp includes only some of those: #ifndef BOOST_UTILITY_HPP #define BOOST_UTILITY_HPP #include <boost/utility/addressof.hpp> #include <boost/utility/base_from_member.hpp> #include <boost/utility/binary.hpp> #include <boost/utility/enable_if.hpp> #include <boost/checked_delete.hpp> #include <boost/next_prior.hpp> #include <boost/noncopyable.hpp> #endif // BOOST_UTILITY_HPP Thanks. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-utility-convention-inconsistencies… Sent from the Boost - Dev mailing list archive at Nabble.com.

2 1