May 2011 - Boost - lists.boost.org

Re: [boost] [BOOST CORE C++ Feature] the super or base keyword for C++
by tymofey 03 May '11

03 May '11

>>Mathias Gaunard 01 May 2011 21:25:53 >>You'd have to use SFINAE to tell whether B1::j exists and use B2::j otherwise. Seems like an unneeded complication to me. Why not just always use B2::j ?

2 1

Checking interest: reflectable types
by Noah Roberts 03 May '11

03 May '11

In my work I've developed a sort of reflection library for C++. There are still many problems to solve before it could near real reflection but I don't believe they are insoluble. It works much like fusion maps except that you can extend them through inheritance. In fact, my current implementation uses fusion to do its thing and with some minor changes to fusion::map it could provide the base. There is a boost.reflection proposal out there that is meant to work with boost.extension. This one is a bit different in that you're not additionally defining data; instead you declare your reflection as you declare your reflectable type through the instantiation of and inheritance from template metafunctions. It's primarily a static/compile-time kind of reflection but can be extended into runtime simply by making your field types a little smarter. Fields describe the data and provide access identifiers. Since they are general types that simply have to have an internal typedef you can attach whatever information is useful. We've done such things as attach valid value ranges, labels, etc... I currently use it do auto-construct property trees for user editing. I plan to use it for scripting/extension. I've had a look at boost.python and it looks like it would be possible, without too much difficulty, to automate python exposure of these types. A coworker with 0 experience in metaprogramming found it fairly easy to feed the types into a structure meant for a report design and printing library. This isn't a promise to actually do anything. I'm just gauging how much, if any interest there is to decide if I want to go to the trouble of hobby developing a publicly available and usable version.

4 11

Proposed date-time patch [ Refs #2475 ]
by Marshall Clow 03 May '11

03 May '11

Here's a proposed patch for ticket #2475. https://svn.boost.org/trac/boost/ticket/2475 Anyone love it? Hate it? Index: ../../../boost/date_time/tz_db_base.hpp =================================================================== --- ../../../boost/date_time/tz_db_base.hpp (revision 71667) +++ ../../../boost/date_time/tz_db_base.hpp (working copy) @@ -166,22 +166,26 @@ //! Constructs an empty database tz_db_base() {} + //! Process csv data stream, may throw exceptions + /*! May throw bad_field_count exceptions */ + void load_from_stream(std::ifstream &ifs) + { + std::string buff; + while( std::getline(ifs, buff)) + parse_string(buff); + } + //! Process csv data file, may throw exceptions /*! May throw data_not_accessible, or bad_field_count exceptions */ void load_from_file(const std::string& pathspec) { - string_type in_str; - std::string buff; - std::ifstream ifs(pathspec.c_str()); - if(!ifs){ + if(!ifs) boost::throw_exception(data_not_accessible(pathspec)); - } + + std::string buff; std::getline(ifs, buff); // first line is column headings - - while( std::getline(ifs, buff)) { - parse_string(buff); - } + load_from_stream(ifs); } //! returns true if record successfully added to map -- Marshall

2 2

[website] Suggestions
by Stephan T. Lavavej 03 May '11

03 May '11

It would be wonderful if: 1. On the main page, there was a direct link to the current version's documentation. Currently, you have to click Documentation, then "1.46.1 - Current Release". (Actually, I just noticed that a direct link does exist - Libraries under Welcome. I was hoping for a big blue button saying GET DOCS.) 2. There was a terse list of links to each library's documentation. The master list currently mentions 6 additional pieces of information for each library (Summary, Authors, First Release, Standard, Build, and Categories). That's nice, but it makes finding library X's documentation significantly more tedious than it has to be (I count 105 libraries in 1.46.1 - that's a lot of scrolling!). I suspect that even beginners don't need information other than the Summary 99% of the time. The current info should be preserved somewhere, but clicking on a release's documentation should bring up a terse list first. http://cid-e66e02dc83efb165.office.live.com/self.aspx/docs/boost.html is a horribly ugly preview of what I'm suggesting (because some libraries have long summaries, I've arbitrarily truncated them; ideally, each library would have a single-line summary at reasonable browser widths). 3. http://boost.org didn't redirect to http://www.boost.org . Even better, if the reverse happened ("Class B", according to http://no-www.org/faq.php ). Clearly, this is the most important issue of all. :-> Stephan T. Lavavej Visual C++ Libraries Developer

5 4

[locale] Review results for Boost.Locale library
by Chad Nelson 03 May '11

03 May '11

The formal review of Artyom Beilis' Boost.Locale library, originally scheduled to run from April 7th through the 16th and extended through the 22nd, is now finished. Fifteen people cast votes on it, ten for acceptance and five against. Though not overwhelming, the two-to-one majority clearly indicates the consensus of the list. As such: The Boost.Locale library IS ACCEPTED into Boost. The details follow, starting with the voters in favor, in the order their reviews were received: * John Bytheway * Steven Watanabe * Sebastian Redl * Fabio Fracassi ("possibly conditional") * Noah Roberts * Steve Bush * Volker Lukas * Paul A. Bristow * Matus Chochlik * Gevorg Voskanyan Those opposed: * Ryou Ezoe * Phil Endecott (but "borderline") * Edward Diener * Mathias Gaunard * Vincente BOTET ("count my vote as 1/2 or 1/4 vote") There was also an early off-list review from Darren Cook which did not include a vote, only listing issues. There was a great deal of discussion around the library, and a number of issues detailed. The major ones (and some less major ones that were repeated by several reviewers) are summarized below, along with the initials of the reviewer(s) who brought them up and Artyom's responses. Note that although I followed the discussions closely, these are only the issues brought up in the formal reviews themselves. * Issue: date_time interface uses enums for periods, which is error prone and inconsistent with other date/time libraries. (JB) * Response: Will be addressed. * Issue: Reference documentation needs more detail or some things not clear; some terms used in the documentation are not defined or are defined too briefly; can't find headers that items are defined in from the documentation. (JB, SW, FF, PE, ED, MC) * Response: Will be addressed. * Issue: There are no prev/next links in the documentation, or tutorial can't easily be navigated. (DC, JB, SR, FF, MC) * Response: Looking into it. * Issue: Few examples include output. (JB) * Response: Will be addressed. * Issue: No examples in Asian languages; the library may have design flaws that are not apparent without them. (DC) * Response: [Artyom has indicated to me (privately) that he's adding such examples. -- CN] * Issue: The translation system requires narrow-character tags, making it English-centric. (RE, ED) * Response: The library implements the most popular and most widely used message-catalog format. It is not perfect, but it is the best system currently available. There may be a work-around if you really must use wide-character languages under Windows. * Issue: Support for wchar_t/UTF-16 is unclear. (RE, ED) * Response: Wide characters are fully supported. * Issue: Doesn't support Win32 API as a backend. (RE) * Response: Misunderstanding, Win32 API backend is fully supported. * Issue: boost::locale::format is not compatible with boost::format. (FF, NR) * Response: boost::format is too limited for use in localization, and throws on any error, which means that a translator error could crash the program. * Issue: boost::locale::date_time is not compatible with boost::date_time. (FF) * Response: An unavoidable consequence of the differences between them, which are necessary due to support for locale independence and non-Gregorian calendars. * Issue: Boundary analysis is only available when using ICU. (FF) * Response: At present, only the ICU backend supports proper boundary analysis. * Issue: Little documentation on the toolchain needed to extract strings and translate them, or the versions required. (FF, NR) * Response: Will be addressed. * Issue: Concerns about relying on GPL/LGPL-licensed tools, or their availability on all platforms, or recommendations to write a Boost version of these tools. (NR) * Response: Reimplementing these is non-trivial and unnecessary; the licensing for these tools does not affect the programs developed with them. All are available for all platforms; will add explicit instructions for getting the latest versions for Windows. * Issue: Use of strings instead of symbols for language and encoding makes run-time errors that could be compile-time errors. The most common ones should be symbols. (PE) * Response: There are dozens of character encodings, and even more locales, and no way to determine which ones are the most common. Not all encodings are supported by all backends or OS configurations. Names ignore case and non-alphanumeric characters, which should minimize errors that could be generated from them. utf_to_utf transcoding will be added. * Issue: Error handling (in conversions) is very basic. (PE) * Response: An unavoidable limitation of the backends. * Issue: Code could use more commenting. (PE, VL) * Response: Noted, will be addressed in the future. * Issue: Some documentation phrasing is confusing, or could use a native English speaker's input. (SR, VL) * Response: Will be addressed as discovered. * Issue: There are no lists of valid language, country, encoding, or variant strings. (ED) * Response: Listed in standards ISO-639 and ISO-3166, which are referenced in the library's documentation. These standards are updated occasionally, and should be referred to directly for the latest information. * Issue: Only works on contiguous, entirely-in-memory strings. (MG) * Response: All current backends require this, and it satisfies the vast majority of use-cases. * Issue: Boundary analysis goes through the entire string and returns a vector of positions. (MG) * Response: Not perfect, but given the limitations of the existing backends, it is reasonable. * Issue: The library's interface is not generic enough, or independent enough of the libraries that it wraps. (VB) * Response: The interface is similar to that of every other i18n library, and should make as few assumptions as possible. It should not be changed. * Issue: The date-time code should be merged into Boost.DateTime. (VB) * Response: Date-time code is locale-dependent by its nature, and is more natural in Boost.Locale. Updating Boost.DateTime to do everything that Boost.Locale's library does would require a lot of work, and in all the time it has existed, only the Gregorian calendar has been implemented. There are Boost libraries that overlap others, so this is not a novelty. -- Chad Nelson Oak Circle Software, Inc. * * *

18 71

[BOOST CORE C++ Feature] The super or base keyword for C++
by Max Hölzer 03 May '11

03 May '11

Hello, i was wondering if it makes sens to add the well known super or base keyword to the C++ language in a generic way. Here I have a simple example on how it would make inherited base or super class overloaded function calls easier. Example 1: class A { public: virtual void print() { std::cout << "A" << std::endl; } }; class B : public A { public: virtual void print() { std::cout << "B" << std::endl; std::cout << "super call "; A::print(); } }; class C : public B { public: virtual void print() { std::cout << "C" << std::endl; std::cout << "super call "; B::print(); } }; int main(int argc, char* argv[]) { A a; B b; C c; a.print(); // Prints A b.print(); // Prints B and super call A c.print(); // Prints C and super call B super call A return 0; } Adding a template class superable would avoid one to write the explicit base or super class name. Example 2: namespace boost { template<typename T> class superable : public T { public: typedef T super; // C++ and java style typedef T base; // C# style }; } class A { public: virtual void print() { std::cout << "A" << std::endl; } }; class B : boost::superable<A> { public: virtual void print() { std::cout << "B" << std::endl; std::cout << "super call "; super::print(); // C++ and java style call } }; class C : boost::superable<B> { public: virtual void print() { std::cout << "C" << std::endl; std::cout << "super call "; base::print(); // C# style call } }; int main(int argc, char* argv[]) { A a; B b; C c; a.print(); // Prints A b.print(); // Prints B and super call A c.print(); // Prints C and super call B super call A return 0; } If somebody could add this to the core boost library, that would be great. Sincerely yours, Max

2 1

[Boost.Log] compilation on msvc 2010 fail.
by Kim Kuen Tang 03 May '11

03 May '11

Hi all, i try to compile Boost.Log for msvc 2010. But it somehow fails. Please see the errors below. Is the msvc-10.0 compiler supported? Thanks for any comments Regards, Kim compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime-link-s tatic\threading-multi\event_log_backend.obj event_log_backend.cpp .\boost/log/detail/universal_path.hpp(46) : error C2039: 'external_string_type' : is not a member of 'boost::filesystem3::path' .\boost/filesystem/v3/path.hpp(54) : see declaration of 'boost::filesyst em3::path' .\boost/log/detail/universal_path.hpp(46) : error C2065: 'external_string_type' : undeclared identifier .\boost/log/detail/universal_path.hpp(49) : error C3203: 'is_same' : unspecializ ed class template can't be used as a template argument for template parameter 'T 1', expected a real type .\boost/log/detail/universal_path.hpp(49) : error C2955: 'boost::is_same' : use of class template requires template argument list .\boost/type_traits/is_same.hpp(37) : see declaration of 'boost::is_same ' .\boost/log/detail/universal_path.hpp(49) : error C2955: 'boost::mpl::if_' : use of class template requires template argument list .\boost/mpl/if.hpp(56) : see declaration of 'boost::mpl::if_' .\boost/log/detail/universal_path.hpp(53) : error C2039: 'basic_path' : is not a member of 'boost::filesystem' .\boost/log/detail/universal_path.hpp(53) : error C2065: 'basic_path' : undeclar ed identifier .\boost/log/detail/universal_path.hpp(53) : error C2988: unrecognizable template declaration/definition .\boost/log/detail/universal_path.hpp(53) : error C2059: syntax error : 'const' .\boost/log/detail/universal_path.hpp(64) : error C2143: syntax error : missing ';' before '<' .\boost/log/detail/universal_path.hpp(64) : error C2913: explicit specialization ; 'boost::log_mt_nt5::aux::make_path' is not a specialization of a class templat e .\boost/log/detail/universal_path.hpp(64) : error C2059: syntax error : '<' .\boost/log/detail/universal_path.hpp(65) : error C2143: syntax error : missing ';' before '{' .\boost/log/detail/universal_path.hpp(65) : error C2447: '{' : missing function header (old-style formal list?) .\boost/log/detail/universal_path.hpp(74) : error C2913: explicit specialization ; 'boost::log_mt_nt5::aux::make_path' is not a specialization of a class templat e .\boost/log/sinks/event_log_backend.hpp(963) : error C2061: syntax error : ident ifier 'basic_path' .\boost/log/sinks/event_log_backend.hpp(1048) : see reference to class t emplate instantiation 'boost::log_mt_nt5::sinks::basic_event_log_backend<CharT>' being compiled .\boost/log/sinks/event_log_backend.hpp(1042) : warning C4346: 'boost::log_mt_nt 5::aux::universal_path' : dependent name is not a type prefix with 'typename' to indicate a type .\boost/log/sinks/event_log_backend.hpp(1042) : error C2061: syntax error : iden tifier 'universal_path' libs\log\src\event_log_backend.cpp(494) : error C2275: 'boost::log_mt_nt5::aux:: universal_path' : illegal use of this type as an expression libs\log\src\event_log_backend.cpp(494) : warning C4346: 'boost::log_mt_nt5::aux ::universal_path' : dependent name is not a type prefix with 'typename' to indicate a type libs\log\src\event_log_backend.cpp(494) : error C2143: syntax error : missing ') ' before 'const' libs\log\src\event_log_backend.cpp(494) : error C2182: 'construct' : illegal use of type 'void' libs\log\src\event_log_backend.cpp(494) : error C2350: 'boost::log_mt_nt5::sinks ::basic_event_log_backend<CharT>::construct' is not a static member libs\log\src\event_log_backend.cpp(498) : error C2059: syntax error : ')' libs\log\src\event_log_backend.cpp(532) : error C2143: syntax error : missing '; ' before '{' libs\log\src\event_log_backend.cpp(532) : error C2447: '{' : missing function he ader (old-style formal list?) ..\boost/log/sinks/event_log_backend.hpp(963) : error C2039: 'basic_path' : is no t a member of 'boost::filesystem' libs\log\src\event_log_backend.cpp(612) : see reference to class templat e instantiation 'boost::log_mt_nt5::sinks::basic_event_log_backend<CharT>' being compiled with [ CharT=char ] ..\boost/log/sinks/event_log_backend.hpp(963) : error C2039: 'basic_path' : is no t a member of 'boost::filesystem' ..\boost/log/sinks/event_log_backend.hpp(963) : error C2061: syntax error : ident ifier 'basic_path' ..\boost/log/sinks/event_log_backend.hpp(963) : error C2039: 'basic_path' : is no t a member of 'boost::filesystem' libs\log\src\event_log_backend.cpp(616) : see reference to class templat e instantiation 'boost::log_mt_nt5::sinks::basic_event_log_backend<CharT>' being compiled with [ CharT=wchar_t ] ..\boost/log/sinks/event_log_backend.hpp(963) : error C2039: 'basic_path' : is no t a member of 'boost::filesystem' ..\boost/log/sinks/event_log_backend.hpp(963) : error C2061: syntax error : ident ifier 'basic_path' call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" x86 >nul cl /Zm800 -nologo @"bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime- link-static\threading-multi\event_log_backend.obj.rsp" ....failed compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runt ime-link-static\threading-multi\event_log_backend.obj... compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime-link-s tatic\threading-multi\nt6_event_log_backend.obj nt6_event_log_backend.cpp compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime-link-s tatic\threading-multi\debug_output_backend.obj debug_output_backend.cpp ....skipped <pbin.v2\libs\log\build\msvc-10.0\release\link-static\runtime-link-st atic\threading-multi>libboost_log-vc100-mt-s-1_46_1.lib for lack of <pbin.v2\lib s\log\build\msvc-10.0\release\link-static\runtime-link-static\threading-multi>te xt_file_backend.obj... ....skipped <pstage\lib>libboost_log-vc100-mt-s-1_46_1.lib for lack of <pbin.v2\l ibs\log\build\msvc-10.0\release\link-static\runtime-link-static\threading-multi> libboost_log-vc100-mt-s-1_46_1.lib... compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime-link-s tatic\threading-multi\parser_utils.obj parser_utils.cpp compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime-link-s tatic\threading-multi\init_from_stream.obj init_from_stream.cpp compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime-link-s tatic\threading-multi\init_from_settings.obj init_from_settings.cpp ..\boost/log/detail/universal_path.hpp(46) : error C2039: 'external_string_type' : is not a member of 'boost::filesystem3::path' .\boost/filesystem/v3/path.hpp(54) : see declaration of 'boost::filesyst em3::path' ..\boost/log/detail/universal_path.hpp(46) : error C2065: 'external_string_type' : undeclared identifier ..\boost/log/detail/universal_path.hpp(49) : error C3203: 'is_same' : unspecializ ed class template can't be used as a template argument for template parameter 'T 1', expected a real type ..\boost/log/detail/universal_path.hpp(49) : error C2955: 'boost::is_same' : use of class template requires template argument list .\boost/type_traits/is_same.hpp(37) : see declaration of 'boost::is_same ' ..\boost/log/detail/universal_path.hpp(49) : error C2955: 'boost::mpl::if_' : use of class template requires template argument list .\boost/mpl/if.hpp(56) : see declaration of 'boost::mpl::if_' ..\boost/log/detail/universal_path.hpp(53) : error C2039: 'basic_path' : is not a member of 'boost::filesystem' ..\boost/log/detail/universal_path.hpp(53) : error C2065: 'basic_path' : undeclar ed identifier ..\boost/log/detail/universal_path.hpp(53) : error C2988: unrecognizable template declaration/definition ..\boost/log/detail/universal_path.hpp(53) : error C2059: syntax error : 'const' ..\boost/log/detail/universal_path.hpp(64) : error C2143: syntax error : missing ';' before '<' ..\boost/log/detail/universal_path.hpp(64) : error C2913: explicit specialization ; 'boost::log_mt_nt5::aux::make_path' is not a specialization of a class templat e ..\boost/log/detail/universal_path.hpp(64) : error C2059: syntax error : '<' ..\boost/log/detail/universal_path.hpp(65) : error C2143: syntax error : missing ';' before '{' ..\boost/log/detail/universal_path.hpp(65) : error C2447: '{' : missing function header (old-style formal list?) ..\boost/log/detail/universal_path.hpp(74) : error C2913: explicit specialization ; 'boost::log_mt_nt5::aux::make_path' is not a specialization of a class templat e ..\boost/log/sinks/text_file_backend.hpp(338) : warning C4346: 'boost::log_mt_nt5 ::aux::universal_path' : dependent name is not a type prefix with 'typename' to indicate a type .\boost/log/sinks/text_file_backend.hpp(524) : see reference to class te mplate instantiation 'boost::log_mt_nt5::sinks::basic_text_file_backend<CharT>' being compiled ..\boost/log/sinks/text_file_backend.hpp(338) : error C2146: syntax error : missi ng ';' before identifier 'path_type' ..\boost/log/sinks/text_file_backend.hpp(338) : error C2838: 'universal_path' : i llegal qualified name in member declaration ..\boost/log/sinks/text_file_backend.hpp(338) : error C4430: missing type specifi er - int assumed. Note: C++ does not support default-int ..\boost/log/sinks/text_file_backend.hpp(509) : error C2061: syntax error : ident ifier 'path_type' ..\boost/log/sinks/text_file_backend.hpp(519) : error C2061: syntax error : ident ifier 'path_type' ..\boost/log/sinks/text_multifile_backend.hpp(62) : warning C4346: 'boost::log_mt _nt5::aux::universal_path' : dependent name is not a type prefix with 'typename' to indicate a type .\boost/log/sinks/text_multifile_backend.hpp(137) : see reference to cla ss template instantiation 'boost::log_mt_nt5::sinks::file::file_name_composer_ad apter<FormatterT>' being compiled ..\boost/log/sinks/text_multifile_backend.hpp(62) : error C2146: syntax error : m issing ';' before identifier 'result_type' ..\boost/log/sinks/text_multifile_backend.hpp(62) : error C2838: 'universal_path' : illegal qualified name in member declaration ..\boost/log/sinks/text_multifile_backend.hpp(62) : error C4430: missing type spe cifier - int assumed. Note: C++ does not support default-int ..\boost/log/sinks/text_multifile_backend.hpp(74) : error C2653: 'result_type' : is not a class or namespace name ..\boost/log/sinks/text_multifile_backend.hpp(74) : error C2065: 'value_type' : u ndeclared identifier ..\boost/log/sinks/text_multifile_backend.hpp(77) : error C3203: 'is_same' : unsp ecialized class template can't be used as a template argument for template param eter 'T1', expected a real type ..\boost/log/sinks/text_multifile_backend.hpp(77) : error C2955: 'boost::is_same' : use of class template requires template argument list .\boost/type_traits/is_same.hpp(37) : see declaration of 'boost::is_same ' ..\boost/log/sinks/text_multifile_backend.hpp(85) : error C2653: 'result_type' : is not a class or namespace name ..\boost/log/sinks/text_multifile_backend.hpp(126) : error C2143: syntax error : missing ';' before '(' ..\boost/log/sinks/text_multifile_backend.hpp(126) : error C4430: missing type sp ecifier - int assumed. Note: C++ does not support default-int ..\boost/log/sinks/text_multifile_backend.hpp(127) : error C4430: missing type sp ecifier - int assumed. Note: C++ does not support default-int ..\boost/log/sinks/text_multifile_backend.hpp(177) : warning C4346: 'boost::log_m t_nt5::aux::universal_path' : dependent name is not a type prefix with 'typename' to indicate a type .\boost/log/sinks/text_multifile_backend.hpp(233) : see reference to cla ss template instantiation 'boost::log_mt_nt5::sinks::basic_text_multifile_backen d<CharT>' being compiled ..\boost/log/sinks/text_multifile_backend.hpp(177) : error C2146: syntax error : missing ';' before identifier 'path_type' ..\boost/log/sinks/text_multifile_backend.hpp(177) : error C2838: 'universal_path ' : illegal qualified name in member declaration ..\boost/log/sinks/text_multifile_backend.hpp(177) : error C4430: missing type sp ecifier - int assumed. Note: C++ does not support default-int ..\boost/log/sinks/text_multifile_backend.hpp(180) : error C2065: 'path_type' : u ndeclared identifier ..\boost/log/sinks/event_log_backend.hpp(963) : error C2061: syntax error : ident ifier 'basic_path' .\boost/log/sinks/event_log_backend.hpp(1048) : see reference to class t emplate instantiation 'boost::log_mt_nt5::sinks::basic_event_log_backend<CharT>' being compiled ..\boost/log/sinks/event_log_backend.hpp(1042) : warning C4346: 'boost::log_mt_nt 5::aux::universal_path' : dependent name is not a type prefix with 'typename' to indicate a type ..\boost/log/sinks/event_log_backend.hpp(1042) : error C2061: syntax error : iden tifier 'universal_path' libs\log\src\init_from_settings.cpp(105) : warning C4346: 'boost::log_mt_nt5::au x::universal_path' : dependent name is not a type prefix with 'typename' to indicate a type libs\log\src\init_from_settings.cpp(105) : error C2146: syntax error : missing ' ;' before identifier 'any_cast_to_path' libs\log\src\init_from_settings.cpp(105) : error C2433: 'boost::log_mt_nt5::aux: :universal_path' : 'inline' not permitted on data declarations libs\log\src\init_from_settings.cpp(105) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int libs\log\src\init_from_settings.cpp(105) : error C2377: 'boost::log_mt_nt5::aux: :universal_path' : redefinition; typedef cannot be overloaded with any other sym bol .\boost/log/detail/universal_path.hpp(49) : see declaration of 'boost::l og_mt_nt5::aux::universal_path' libs\log\src\init_from_settings.cpp(105) : error C2888: 'if_c<T1::value,T2,T3>:: type boost::log_mt_nt5::aux::universal_path' : symbol cannot be defined within n amespace 'anonymous-namespace' libs\log\src\init_from_settings.cpp(105) : error C2888: 'int boost::log_mt_nt5:: aux::universal_path' : symbol cannot be defined within namespace 'anonymous-name space' libs\log\src\init_from_settings.cpp(105) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int libs\log\src\init_from_settings.cpp(105) : error C2143: syntax error : missing ' ,' before '*' call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" x86 >nul cl /Zm800 -nologo @"bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime- link-static\threading-multi\init_from_settings.obj.rsp" ....failed compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runt ime-link-static\threading-multi\init_from_settings.obj... compile-c-c++ bin.v2\libs\log\build\msvc-10.0\release\link-static\runtime-link-s tatic\threading-multi\filter_parser.obj filter_parser.cpp

2 4

[lambda] Diff with Boost.Phoenix (for lambdas)
by lcaminiti 02 May '11

02 May '11

Hello all, Recently I used both Boost.Lambda and Boost.Phoenix to implement lambda functions. Why does Boost have two libraries that implement lambda functions? In my (limited) experience, Boost.Phoenix is more powerful than Boost.Lambda (and it has comparable run-times even if it has larger compile-times) plus Boost.Phoenix can do much more than "just" lambdas. * Is there anything that Boost.Lambda can do more than Boost.Phoenix? * Is there any application domain where using Boost.Lambda makes more sense than using Boost.Phoenix? Thank you. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-lambda-Diff-with-Boost-Phoenix-for… Sent from the Boost - Dev mailing list archive at Nabble.com.

1 0

[filesystem] Decomposition of filenames beginning with period?
by Beman Dawes 01 May '11

01 May '11

Boost.Filesystem class path views filenames as being made up of a stem and an extension. My Windows Users directory includes files ".gitconfig" and ".netrc". The current class path implementation views these as having extensions of ".gitconfig" and ".netrc", respectively, and empty stems. To me, that's a bit counter intuitive. I guess I view filenames as always having stems, but extensions being optional. But I don't view that as a strong enough argument to change anything. Does anyone have a stronger argument than intuition for changing or retaining the current behavior? --Beman

13 20

Re : [Block Pointer] make_block
by Pierre Morcello 01 May '11

01 May '11

Hi Phil, >>> Phil Bouchard <philippe(a)fornux.com> wrote : >>> We can see it in action >>> in the following example: >>> https://svn.boost.org/svn/boost/sandbox/block_ptr/libs/smart_ptr/example/bl… A detail : I think you could improve your sample by replacing __FUNCTION__ by BOOST_CURRENT_FUNCTION (which is more portable), or by writing directly the name of the function. >>>Is it time for a review? I looked for automated tests in the sandbox directory (not examples) and I did not find any. Instead of doing "cout", you could use a class like that : class ForTests { static int counter; // incremented at each construction int id; // id = current value of the counter in the constructor static std::vector<int> destructionOrder; }; Each destruction pushes the id in the destructionOrder vector. Then at the end of the program you just need to compare the content of destructionOrder with what you should expect (and return 1 or 0). Also the same might be done for construction. Good job BTW, and good luck for the review, Pierre Morcello

2 4