- Boost - lists.boost.org

[tti] Moving TTI to release
by Edward Diener 19 May '13

19 May '13

Do I have to do anything further to move TTI from the trunk to the release branch for Boost 1.54 ? If so, please inform me of it as I am happy that TTI can be part of the 1.54 release, and I believe that the cutoff date for new libraries is tomorrow. Edward Diener

2 4

[gil] Ok to merge new gil's extension to release branch?
by Christian Henning 19 May '13

19 May '13

Hi, is it ok? The merge would include io, toolbox, numerics and some other changes to gil's code itself. Regards, Christian

6 92

[trac] Request to add TTI library to trac system
by Edward Diener 18 May '13

18 May '13

Would the TTI library pleased be added to the Boost trac system ? I am the owner of the component and my trac ID is 'eldiener'. Edward Diener

2 2

Getting regression test command lines
by Edward Diener 18 May '13

18 May '13

It is not possible in the regression tests I see on the Boost website to get the full command lines for a regression test. The reason for this is that the regression test uses a command response file and the contents of the command response are not being shown. Atypical example might be: cl /Zm800 -nologo @"D:\BoostRT\results\boost\bin.v2\libs\tti\test\test_has_data_compile.test\msvc-9.0~w\dbg\stdlb-stlpr-5.2~9\test_has_data_compile.obj.rsp Without knowing what the command response file contains it is impossible to know what the command options are for the test. This makes it very difficult to duplicate the reason for a failure in the online regression tests.

2 2

[trac] No `tti` component
by Michel Morin 18 May '13

18 May '13

Hi, There is no `tti` component in trac yet. Thanks, Michel

4 4

[1.54.0] [log] Permission to merge to release
by Andrey Semashev 17 May '13

17 May '13

Hi, I'd like to ask for permission to merge Boost.Log to the release branch. All test issues are resolved, although some MinGW testers haven't run the tests for 2 weeks and haven't updated the report. RDC-VC10 tester also didn't clean the previous test results so the report is not showing the actual results (other MSVC testers are green). The util_dynamic_type_dispatcher and util_static_type_dispatcher rows should be ignored, these tests were renamed to util_dynamic_type_disp and util_static_type_disp, respectively.

2 3

[Interprocess] Named Pipe status
by Geoff Shannon 17 May '13

17 May '13

Hi, I'm interested in writing a named pipe implementation for Boost.Interprocess (mostly since I would like to use it myself!). I was curious if anyone knew if there has already been design work done on a desired interface, or if there is actual work underway (I wasn't able to find any evidence of either but I'm normally just a boost user). Also, any comments/suggestions on what would be desired out of such a feature are much appreciated. thanks, -- Geoff Nothing is ever easy.

2 1

[string_ref] Add an equality operator between string_ref and char*
by Nicola Bizzoca 17 May '13

17 May '13

Hi, string_ref currently lacks of a simple and efficient way to compare a string_ref data to a C style string The current way that string_ref promotes is: string_ref_data.compare("boost(a)lists.boost.org") == 0 It's error prone (always checking for 0, < 0, > 0) and involves a series of implicit casting (from char* to string, and from string to string view) The same it's valid for comparing string_ref to string, but is this case an implicit casting from string to string_ref is much less expensive

1 0

[tti] Will TTI be in 1.54?
by Jeremiah Willcock 17 May '13

17 May '13

Is TTI planned to be in the next release? I have some changes to Boost.Graph that have been in the trunk for a while but depend on TTI to enable backwards compatibility, and it would be nice to have them in a release. Will that be available in the release branch soon so I can test against it? Thank you. -- Jeremiah Willcock

3 5

[config] BOOST_FORCEINLINE for clang
by Vicente J. Botet Escriba 16 May '13

16 May '13

Hi, I would like to add the definition of BOOST_FORCEINLINE for clang when __has_attribute(always_inline) // BOOST_FORCEINLINE ---------------------------------------------// #if !defined(BOOST_FORCEINLINE) # if defined(_MSC_VER) # define BOOST_FORCEINLINE __forceinline +# elif defined(__clang__) +# if __has_attribute(always_inline) +# define BOOST_FORCEINLINE inline __attribute__((always_inline)) +# endif # elif defined(__GNUC__) && __GNUC__ > 3 # define BOOST_FORCEINLINE inline __attribute__ ((always_inline)) # else Could I commit it? Best, Vicente

7 11