August 2007 - Boost - lists.preview.boost.org

Re: [boost] [Boost-users] [ScopeExit/Typeof] Can't build simple test in debugmode (MSVC 7.1 and 8.0)
by Christian Larsen 14 Aug '07

14 Aug '07

Hi, I've moved this to the dev list, because it should probably be mentioned in the documentation somewhere. I'm not sure whether it belongs in Typeof or ScopeExit. I've tried building the hello.cpp example that comes with ScopeExit with the same results (as in my original message). I think I have narrowed down the cause. Building fails whenever "Program Database for Edit & Continue (/ZI)" is set in the project properties. Changing this to "Program Database (/Zi)" or any other fixes the problem. Is this a compiler bug? I never use Edit & Continue anyway, but I thought it might be helpful to others to mention this problem somewhere. Best regards, Christian Larsen Christian Larsen wrote: > I'm trying build a very simple test program using ScopeExit (just > downloaded > from the link in the review notice: > http://boost- > consulting.com/vault/index.php?action=downloadfile&filename=sco > pe_exit-0.04.tar.gz&directory=& ). I'm using a brand new download of Boost > 1.34.1 with it. The following code builds and runs fine in release mode in > both VC7.1 and 8.0, but fails to build in debug mode in both versions. I > also tried specifying the BOOST_TYPEOF_COMPLIANT in MSVC7.1 debug but to > no > avail - I just get some other errors. I couldn't find any indication of > what > would cause this difference between debug/release builds. I tried > disabling > optimizations in release mode to check whether this would cause release > mode > to fail, too, but it didn't. Any help would be appreciated. > > > > Code: > > #include <iostream> > #include <boost/scope_exit.hpp> > > int main(int argc, char* argv[]) > { > bool commit = false; > > BOOST_SCOPE_EXIT( (commit) ) { > if( !commit ) > std::cerr << "Not committed!\n"; > } BOOST_SCOPE_EXIT_END > > //commit = true; > return 0; > } [SNIP] > Building debug mode MSVC 7.1 (with BOOST_TYPEOF_COMPLIANT): > > Compiling... > ScopeExitTest.cpp > using typeof emulation > d:\Development\Misc\ScopeExitTest\ScopeExitTest.cpp(8) : error C2440: > 'type > cast' : cannot convert from 'long' to > 'main::commit_boost_scope_exit_nested_typeof' > Source or target has incomplete type > d:\Development\Misc\ScopeExitTest\ScopeExitTest.cpp(8) : error C2143: > syntax > error : missing ';' before ':' > d:\Development\Misc\ScopeExitTest\ScopeExitTest.cpp(8) : error C2143: > syntax > error : missing ';' before ':' > d:\Development\Misc\ScopeExitTest\ScopeExitTest.cpp(8) : error C2143: > syntax > error : missing ';' before '{' > d:\Development\Misc\ScopeExitTest\ScopeExitTest.cpp(8) : error C2039: > 'type' > : is not a member of 'operator``global namespace''' > d:\Development\Misc\ScopeExitTest\ScopeExitTest.cpp(8) : error C2513: > 'int' > : no variable declared before '=' > d:\Development\Misc\ScopeExitTest\ScopeExitTest.cpp(8) : error C2146: > syntax > error : missing ';' before identifier 'type' > d:\Development\Misc\ScopeExitTest\ScopeExitTest.cpp(8) : error C2065: > 'type' > : undeclared identifier > d:\Development\Misc\ScopeExitTest\ScopeExitTest.cpp(8) : error C2146: > syntax > error : missing ';' before identifier 'commit_boost_scope_exit_typeof' [SNIP]

1 0

Boost.Test documentation update; alpha release
by Gennadiy Rozental 14 Aug '07

14 Aug '07

Hi, I've finally been able to produce alpha release of completely reworked BoostBook based documentation for Boost.Test library. It's still not ready for release and I expect significant changes in both L&F (once I apply latest IBD based style) and content (some articles still missing). But it's in a shape close to what I would like it to be. I would really appreciate any comments to both content (language including) and style. I realize it might not be small undertaking so if you have time for just part of it, please post comments as well. The release is available here: patmedia.net/~rogeeff/html/index.html in patmedia.net/~rogeeff/src you can find sources. Thank you, Gennadiy

3 5

Re: [boost] Boost.Test documentation update; alpha release
by Peter Foley 14 Aug '07

14 Aug '07

Gennadiy, Initial comments (IMO) so far: It might be worthwhile including a section at the beginning to list the standard acronyms and provide a definition for any common terms you use throughout the documentation. There are several instances so far where you use an acronym without specifying what it is. FAQ: "Where the latest version of the Boost Test Library is located?" should read "Where can I find the latest release of the Boost Test Library and Documentation?" - Under this then have these sentences: + "The latest version of the Boost Test Library documentation can always be found online at http://www.boost.org/libs/test" + "To download the latest release of the Boost Test Library code please follow the instructions detailed in the Getting Started Guide located at http://www.boost.org/more/getting_started.html" - It might also be worthwhile adding something here for getting the latest code from Subversion? "I found a bug. Where can I report it?" - To encourage good behaviour it might be worth adding these points under this heading: + To ensure that the author of the library fixes the bug please submit a bug report by: * Submitting a new trac ticket at http://svn.boost.org/trac/boost/newticket. Please ensure that you select the correct milestone and version of boost you are using. It is important that you also select "Test" as the component to ensure speedy notification. * In addition to the above you can send a bug report to the boost users/developers mailing list and/or directly to me (include email address) "I have a request for a new feature. How can I ask for it?" - To encourage good behaviour it might be worth adding these points under this heading: + To ensure appropriate tracking of the feature request it is important to submit this to our tracking database by: * Submitting a new trac ticket at http://svn.boost.org/trac/boost/newticket. Please ensure that you select "Feature Request" in the type of the request. It is important that you also select "Test" as the component to ensure that this is tracked against the Unit Test Framework. * In addition to the above you can send a feature request to the boost users/developers mailing list and/or directly to me (include email address) "How to create test case using the UTF?" - If I am a newbie looking at the Test Library FAQ am I already expected to know what the acronym "UTF" stands for? Also is UTF a standard keyword to search for if I already know about Test Driven Development (TDD)? Looking at the current(/old) FAQ it seems that UTF standards for Unit Test Framework. - It might be worthwhile to rename this to something like "What is the simplest way to write a test in the Boost Test Library?" "How to create test suite using the UTF?" - Similar comments to the above. - Maybe rename this to "What is the easiest way to group similar tests in the Boost Test Library?" --- [ End comments so far ] --- This is as far as I have gone so far I will try to get some more time tomorrow night. If you make the BoostBook file available I will try to update this and then you can do a diff and work out which changes are relevant. Thanks, Peter. - > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 12 Aug 2007 05:26:51 -0400 > From: "Gennadiy Rozental" <rogeeff(a)gmail.com> > Subject: [boost] Boost.Test documentation update; alpha release > To: boost(a)lists.boost.org > Cc: boost-users(a)lists.boost.org, boost-docs(a)lists.boost.org > Message-ID: <f9mjom$kgo$1(a)sea.gmane.org> > > Hi, > > I've finally been able to produce alpha release of completely reworked > BoostBook based documentation for Boost.Test library. It's still not > ready > for release and I expect significant changes in both L&F (once I apply > latest IBD based style) and content (some articles still missing). But > it's > in a shape close to what I would like it to be. > > I would really appreciate any comments to both content (language > including) and style. I realize it might not be small undertaking so if > you > have time for just part of it, please post comments as well. > > The release is available here: > > patmedia.net/~rogeeff/html/index.html > > in patmedia.net/~rogeeff/src you can find sources. > > Thank you, > > Gennadiy

3 2

Re: [boost] [Proto] Tag for invert
by dan marsden 13 Aug '07

13 Aug '07

Argh, complement! Just spotted it, sorry for the noise. Cheers Dan ----- Original Message ---- From: dan marsden <danmarsden(a)yahoo.co.uk> To: Boost <boost(a)lists.boost.org> Sent: Monday, 13 August, 2007 10:32:05 PM Subject: [boost] [Proto] Tag for invert Hi I'm been looking for the tag corresponding to ~a in proto. I couldn't see anything in the tags section of the docs, although its a long list, so apologies if I've just missed it. Cheers Dan ___________________________________________________________ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost ___________________________________________________________ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/

1 0

[Proto] Tag for invert
by dan marsden 13 Aug '07

13 Aug '07

Hi I'm been looking for the tag corresponding to ~a in proto. I couldn't see anything in the tags section of the docs, although its a long list, so apologies if I've just missed it. Cheers Dan ___________________________________________________________ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/

2 1

warning suppression
by Steven Watanabe 13 Aug '07

13 Aug '07

AMDG I ran the attached program on the Subversion trunk. output attached. There are quite a few headers that suppress warnings but fail to restore them. Some of these are harmless and a a few are paired disable/enable headers. In Christ, Steven Watanabe ./boost/archive/detail/abi_prefix.hpp ./boost/archive/detail/abi_suffix.hpp ./boost/archive/impl/basic_xml_grammar.hpp ./boost/asio/detail/pop_options.hpp ./boost/asio/detail/push_options.hpp ./boost/config/compiler/visualc.hpp ./boost/fusion/sequence/container/map/detail/map_lookup.hpp ./boost/fusion/sequence/container/set/detail/set_lookup.hpp ./boost/fusion/support/detail/compiler_config.hpp ./boost/interprocess/allocators/detail/adaptive_node_pool.hpp ./boost/interprocess/allocators/detail/node_pool.hpp ./boost/interprocess/allocators/detail/node_tools.hpp ./boost/interprocess/detail/config_begin.hpp ./boost/interprocess/detail/config_end.hpp ./boost/interprocess/smart_ptr/segment_deleter.hpp ./boost/intrusive/detail/config_begin.hpp ./boost/intrusive/detail/config_end.hpp ./boost/iostreams/detail/config/disable_warnings.hpp ./boost/iostreams/detail/config/enable_warnings.hpp ./boost/operators.hpp ./boost/ptr_container/detail/static_move_ptr.hpp ./boost/python/detail/config.hpp ./boost/python/detail/wrap_python.hpp ./boost/regex/pattern_except.hpp ./boost/regex/v4/regex_workaround.hpp ./boost/serialization/collections_load_imp.hpp ./boost/serialization/detail/stack_constructor.hpp ./boost/serialization/ephemeral.hpp ./boost/serialization/hash_collections_load_imp.hpp ./boost/serialization/nvp.hpp ./boost/serialization/serialization.hpp ./boost/serialization/variant.hpp ./boost/serialization/void_cast.hpp ./boost/spirit/core/primitives/impl/primitives.ipp ./boost/spirit/core/primitives/primitives.hpp ./boost/statechart/detail/rtti_policy.hpp ./boost/statechart/detail/state_base.hpp ./boost/statechart/state_machine.hpp ./boost/static_warning.hpp ./boost/test/detail/enable_warnings.hpp ./boost/test/detail/suppress_warnings.hpp ./boost/test/utils/iterator/ifstream_line_iterator.hpp ./boost/test/utils/nullstream.hpp ./boost/test/utils/runtime/config.hpp ./boost/tuple/detail/tuple_basic_no_partial_spec.hpp ./libs/serialization/src/basic_xml_grammar.ipp ./libs/statechart/example/Camera/Camera.hpp ./libs/statechart/example/Camera/Configuring.hpp ./libs/statechart/example/Camera/Shooting.hpp ./libs/type_traits/test/test.hpp ./libs/wave/samples/cpp_tokens/cpp_tokens_config.hpp ./libs/wave/samples/list_includes/list_includes_config.hpp ./libs/wave/samples/token_statistics/token_statistics.hpp ./libs/wave/samples/waveidl/idl_config.hpp ./tools/quickbook/detail/actions.hpp ./tools/wave/cpp_config.hpp // check_pragmas.cpp // // Copyright (c) 2007 // Steven Watanabe // // Distributed under the Boost Software License, Version 1.0. (See // accompanying file LICENSE_1_0.txt or copy at // http://www.boost.org/LICENSE_1_0.txt) #include <string> #include <iterator> #include <iostream> #include <boost/filesystem.hpp> #include <boost/filesystem/fstream.hpp> #include <boost/regex.hpp> namespace fs = boost::filesystem; boost::regex pragmas("#\\s*pragma\\s+warning\\s*\\(\\s*((push)|(pop)|(disable))"); int main() { fs::recursive_directory_iterator iter("."); fs::recursive_directory_iterator end; for(; iter != end; ++iter) { if(!fs::is_directory(iter->path())) { const std::string extension(fs::extension(iter->path())); if(extension == ".hpp" || extension == ".ipp") { fs::ifstream file(iter->path()); std::string file_contents(std::istreambuf_iterator<char>(file.rdbuf()), std::istreambuf_iterator<char>()); int push_count = 0; boost::regex_iterator<std::string::iterator> regex_iter(file_contents.begin(), file_contents.end(), pragmas); boost::regex_iterator<std::string::iterator> regex_end; for(; regex_iter != regex_end; ++regex_iter) { if((*regex_iter)[2].matched) { ++push_count; } else if((*regex_iter)[3].matched) { --push_count; if(push_count < 0) { std::cout << *iter << std::endl; goto done_with_file; } } else if((*regex_iter)[4].matched) { if(push_count <= 0) { std::cout << *iter << std::endl; goto done_with_file; } } } if(push_count != 0) { std::cout << *iter << std::endl; } done_with_file:; } } } }

13 26

proxies and const
by Eric Niebler 13 Aug '07

13 Aug '07

General design question here. This came up on the user's list, and it made me question something I believed to be true. When writing a proxy for, e.g., a std container, I see two options for handling const. 0) Const-ness depends on the const-ness of the object being proxied: struct vector_proxy { std::vector<int> & vec; typedef std::vector<int>::iterator iterator; typedef std::vector<int>::iterator const_iterator; iterator begin() const { return vec.begin(); } ... }; 1) Const-ness depends on the proxy object itself: struct vector_proxy { std::vector<int> & vec; typedef std::vector<int>::iterator iterator; typedef std::vector<int>::const_iterator const_iterator; iterator begin() { return vec.begin(); } const_iterator begin() const { return vec.begin(); } ... }; I think a loooong time ago, I preferred (1) but these days (0) is more natural for me, but I can't say why, exactly. Just feels like that's how it should be. Thoughts? FWIW, it came up in the context of BOOST_FOREACH's handling of proxies, so it's not (far) off-topic. -- Eric Niebler Boost Consulting www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com

7 16

[GSoC] Boost.Reflection
by Mariano Gabriel Consoni 13 Aug '07

13 Aug '07

Hi List! As you may know, I'm working in GSoC on a project called Boost.Extension/Reflection. The Extensions part of the project is finished (just a few details are missing, its original author is working on that), and I've started to work in Boost.Reflection a month ago. This is a library that brings "Reflection" features to C++. The features that are completed now is that you can reflect a class, setting a name for it and you can add different methods, each one identified with an ID of some type (could be different for each method). Also you should define parameter names and types. Finally, you could use the reflection to call any method (identified with that ID). This mail is just to let you know that, besides it isn't complete, we have committed to the sandbox a working version. It has minimum documentation and some examples. We'll continue working to complete the library, improve docs and bring more examples before and after the end of the program. Feel free to contact me if you have questions. Bye! -- Mariano

1 0

[units] suggestions on examples/tutorials to add
by Matthias Schabel 13 Aug '07

13 Aug '07

Steven and I are trying to finish up the examples and documentation for Boost.Units so that it can, hopefully, be ready in time for inclusion in 1.35. I'd love to hear from anyone who has been using it with feedback on the examples/docs, particularly suggestions for improvements or comments on areas that are unclear or difficult to follow. Matthias

1 0

CLI: A boost command line interpreter based on boost Program Option
by JD 13 Aug '07

13 Aug '07

Hi all, I wrote a little command line interpreter based on the program option library by Vladimir Prus. You can find it here: http://minilien.com/?bNPy1ECuWv. It's not a big thing but can help sometime. You also have the subversion repository there: http://code.google.com/p/clipo/ Let me know what you think. JD

3 4