- Boost - lists.boost.org

State machine framework with dynamic configurability
by David Abrahams 24 Jun '05

24 Jun '05

Cross-posted from c.l.c++.m: -- Dave Abrahams Boost Consulting www.boost-consulting.com

3 3

documentation doesn't build anymore
by Peter Simons 24 Jun '05

24 Jun '05

I can't build the "doc/" directory of the current boost CVS version any longer: budweis:/usr/local/src/boost-current/doc$ bjam --v2 /usr/local/src/boost-current/tools/build/v2/build/feature.jam:193: in feature.attributes from module feature error: "<link-runtime>" is not a valid feature name /usr/local/src/boost-current/tools/build/v2/build/property.jam:409: in property.translate-paths from module property [...] Am I the only one who has that problem? Is there a simple fix, maybe? Any ideas, anyone? Peter

4 10

[Test] [All Library Developers] multiple definitions
by David Abrahams 24 Jun '05

24 Jun '05

I just tried to compile something with the test library and two translation units. Boom! It was this definition, which appears in boost/test/impl/execution_monitor.ipp. signal_handler* signal_handler::s_active_handler = NULL; //!! need to be placed in thread specific storage I can hardly blame Gennadiy, though, having made this mistake myself many times. The reason I noticed this was that I have just started a simple practice that should root out these problems in my own code: I build a program that #includes all my headers in two translation units. For example: // ---- main.cpp ---- #include <boost/python.hpp> extern int f(); int main() { return f(); } // ---- main.cpp ---- #include <boost/python.hpp> int f() { return 0; } Presto! Instant linker errors pointing me at offending definitions. Every library should include a test like the one above. You may be wondering how to work around these issues when you really need header-only capability and can't stick the definition in a source file. In this case, the fix was easy: since the variable in question is a static member, just refactor it into a templated base class. class signal_handler; template <int = 0> struct signal_handler_ { static signal_handler* s_active_handler; }; class signal_handler : signal_handler_<> { ... }; //!! need to be placed in thread specific storage template <int N> signal_handler* signal_handler_<N>::s_active_handler = NULL; When you need a namespace-scope variable, things get a bit more interesting. You might consider sticking one in an unnamed namespace, but then you run a great risk of violating the One Definition Rule (see 3.2 in the standard) when identical template specializations and inline functions that use the variable are instantiated and use distinct objects in two translation units. Boost.Bind's placeholders have this problem. The answer is to initialize a *reference* in the unnamed namespace to a single, common object: namespace whatever { class foo {}; template <class T, int = 0> struct unique_instance { T& get() { static T x; return x; }; }; namespace { foo& bar = unique_instance<foo>::get(); } } -- Dave Abrahams Boost Consulting www.boost-consulting.com

3 10

No regression report e-mails today
by Doug Gregor 24 Jun '05

24 Jun '05

Errors in the fixes to numeric_cast caused a huge number of regressions. I believe they've all been fixed now, but we'll skip the regression report e-mails for today to avoid any false alarms. *Please* everyone be very careful when checking in changes. We're trying to get a release out, and even trivial mistakes can push back this release. Doug

1 0

[inspect] Please mind your tabs, and EOLs.
by Rene Rivera 24 Jun '05

24 Jun '05

http://www.boost.org/regression-logs/inspection_report.html Boost Inspection Report 10421 files scanned 823 directories scanned 461 problems reported problem counts: 16 files with invalid line endings 0 bookmarks with invalid characters 1 invalid urls 268 broken links 49 unlinked files 41 file names too long 66 files with tabs 20 violations of the Boost min/max guidelines -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

1 0

Re: [boost] [serialization] new STATIC_ASSERTION_FAILURE
by Martin Bonner 24 Jun '05

24 Jun '05

----Original Message---- From: Robert Ramey [mailto:ramey@rrsd.com] Sent: 23 June 2005 17:07 To: boost(a)lists.boost.org Subject: Re: [boost] [serialization] new STATIC_ASSERTION_FAILURE > Vladimir Prus wrote: > >>> "all #includes from the boost/archive directory should preceed all >>> #includes from the serialization directory." >> >> This rule means that I can't include >> <boost/serialization/base_object.hpp> >> in my headers, and then in my cpp file first include my headers and >> then archive headers. And I do want to include my header first in >> .cpp, in order to detect any missing includes in the header itself. > > I don't really understand this. Many people (myself included) have a rule that header files are self contained. If you need something in the header file, you #include the header and that is all you have to do. To police this, and to make sure that the program is not compiling "by accident" because every current occurance of the header happens to be preceded by the required headers, the standard form of a file xxx.cpp in my projects is: #include "universal.h" // Absolutely standard includes that would be // boring to include in every header - like windows.h #include "xxx.h" // Prove that xxx.h is self contained. Some people have an even stronger form of the rule without the universal.h - they will have a REAL problem with requiring an order of includes. I read your explanation of why you have the requirement on the order of includes, and it seems to buy some advantages for some people (but not all). It *is* quite a high cost though; not having used serialization, I can't say whether it is worth it. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

2 1

[config] BOOST_NO_LONG_LONG_NUMERIC_LIMITS not detected correctly?
by Markus Schöpflin 24 Jun '05

24 Jun '05

Sample program: ---%<--- #include <limits> #include <iostream> using namespace std; int main() { cout << numeric_limits<long long>::is_specialized << '\n'; cout << numeric_limits<unsigned long long>::is_specialized << '\n'; } --->%--- Compiling and running this on Tru64/CXX with relaxed ANSI mode gives: schoepf@area51:~/net/tmp> cxx -version V6.5-042 -O0 -std ansi -model ansi ./test_ll_limits.cpp && ./a.out 1 1 Compiling and running this on Tru64/CXX with strict ANSI mode gives: schoepf@area51:~/net/tmp> cxx -version V6.5-042 -O0 -std strict_ansi -model ansi ./test_ll_limits.cpp && ./a.out cxx: Warning: ./test_ll_limits.cpp, line 8: the type "long long" is nonstandard cout << numeric_limits<long long>::is_specialized << '\n'; ------------------------------^ cxx: Warning: ./test_ll_limits.cpp, line 9: the type "long long" is nonstandard cout << numeric_limits<unsigned long long>::is_specialized << '\n'; ---------------------------------------^ 0 0 But when running configure in libs/config with CXX="cxx -version V6.5-042 -std strict_ansi -model ansi" bash ./configure, BOOST_NO_LONG_LONG_NUMERIC_LIMITS doesn't get defined in the resulting "user.hpp". The relevant section from the log file looks like this: configure:2190: checking std::numeric_limits<long long> configure:2220: cxx -version V6.5-042 -std strict_ansi -model ansi -o conftest -I./../.. -I./../../libs/config/test -g -DBOOST_NO_CONFIG conftest.cpp -lrt -lm >&5 configure:2223: $? = 0 Why does configure think that the specializations are present? Markus

2 4

Re: [boost] [regex] Boost.Regex and TR1 fundamentally broken?
by Martin Bonner 24 Jun '05

24 Jun '05

John Maddock wrote: > currently in most cases a tolower will do the job, > and even for fairly strict Unicode > conformance a tolower(toupper(c)) will work. You do know that toupper(c) is conceptually broken, don't you? There is at least one character (U+00DF Latin Small Letter Sharp S), whose upper case equivalent in German is TWO characters. Of course, in the case of regular expressions, it might well be acceptable or even best to treat scharfes-es as equivalent to "ss" and then - however I always get nervous when I see people using tolower/toupper in I18N contexts. (Note that tolower is worse, to convert a string to lowercase in German you need a dictionary to decide whether to use "ss" or scharfes-es - and I think that there is a case where you need to interpret the text to decide which word it is! Oh, and finally, this all assumes that the proposed German spelling reforms don't happen because I think they largely eliminate the scharfes-es :-) -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

3 2

[Boost-bugs] [ boost-Feature Requests-1226917 ] Please add support for Intel 9 WIN32
by SourceForge.net 24 Jun '05

24 Jun '05

Feature Requests item #1226917, was opened at 2005-06-24 19:56 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1226917&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Lars Schouw (schouwla) Assigned to: Nobody/Anonymous (nobody) Summary: Please add support for Intel 9 WIN32 Initial Comment: Please add support for the Intel 9.0 for Windows C++ compiler. Lard ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1226917&group_… ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Boost-bugs] [ boost-Support Requests-1226877 ] "boost_regex_vc7_mdid.lib" not found
by SourceForge.net 24 Jun '05

24 Jun '05

Support Requests item #1226877, was opened at 2005-06-24 02:35 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1226877&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: "boost_regex_vc7_mdid.lib" not found Initial Comment: Hello, We have a VC++ application that is built in VS 6.0 that uses Boost libraries (those for VS6.0). We migrated to VS .Net 2003 (VC++ 7.x). We are having trouble with compilation of our application. The error comes at the time of linking which says the file "boost_regex_vc7_mdid.lib" not found. Also, we do not have this lib file. Does anybody have any idea about this file? Did somebody get such a problem ever? Please reply us at: prasadrn(a)hcltech.com subbavr(a)hcltech.com Thanks a lot in advance, Prasad Narwadkar. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1226877&group_… ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0