- Boost - lists.boost.org

Proposal for std::numeric_limits<T>::max_digits10;
by Paul A Bristow 13 Jun '05

13 Jun '05

I attach links to a proposal for very tiny addition to the numeric_limits. It provides an easy way for the novice to ensure that all potentially significant digits are output. For example, for float 6 decimal digits are guaranteed, but 9 may be significant. This is used in Boost test, and should be useful for lexical_cast, serialization etc. Comments, objections, better name suggestions, etc welcome. Paul http://www.hetp.u-net.com/public/Cpp/numeric_limits%20significant%20digits.p df aka http://tinyurl.com/9qxdk Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB +44 1539 561830 +44 7714 330204 mailto: pbristow(a)hetp.u-net.com

1 0

Re: [boost] MPL on IBM-vacpp
by Toon Knapen 13 Jun '05

13 Jun '05

Markus Schöpflin <markus.schoepflin(a)comsoft.de> wrote: >Toon Knapen wrote: > >> As you might have noticed we have succeeded in running regression.py on >IBM. >> In the mean time Joaquin already noted that multi_index was broken. He >also >> suggested that it was probably due to >> BOOST_MPL_CFG_USE_OPERATORS_OVERLOADING. And indeed, adding >> BOOST_WORKAROUND(__IBMCPP__, <= 600 ) to boost/mpl/aux_/config makes >that >> multi_index compiles again (and probably other libs too). > >Better make that BOOST_WORKAROUND(__IBMCPP__, BOOST_TESTED_AT(600) ) Indeed that would be better. > >> So is it OK to add the patch in attachment ? > actually I did not forget the attachment. I forgot though that the mail- client I am currently using always drops the attachment. Well anyway, the patch is straightforward. I will send it again on thursday when I have access again to my development machine. toon

1 0

Text_archives don't support integer types?
by Marcin Tustin 13 Jun '05

13 Jun '05

I'm using the CVS version of Boost from 2005-06-06, and it seems that text archives don't support anything except strings, characters, and the like, specifically not integer types like int. I've grepped the archive includes, and it seems that there are no save methods specified for the integer types (except char) by the text archives, and I get compiler errors like: c:\D2\API\NewClient\EnhancedMessageHandler.h(370) : error C2679: binary '<<' : no operator found which takes a right-hand operand of type 'int' (or there is no acceptable conversion) (with VC7.1) It works when the RHS of << is a variable, but not when it is a function. I take it that this is because with variables, a string is automatically constructed to wrap the int types. This is very confusing, and might well be worth mentioning in the docs. Marcin Tustin IT Innovation Centre 2 Venture Road Chilworth Science Park Southampton, SO16 7NP, UK tel: +44 23 8076 0834 fax: +44 23 8076 0833 mailto:mt@it-innovation.soton.ac.uk http://www.it-innovation.soton.ac.uk

1 0

[autolink] conflicts with new toolset names
by Joaquín Mª López Muñoz 13 Jun '05

13 Jun '05

autolink assumes the following toolset tags for libraries generated under the MSVC familiy of compilers: 6.0, 6.5 --> "v6" 7.0 --> "vc7" 7.1 --> "vc71" 8.0 --> "vc80" Yet tools/build/v1/boost-base.jam does the following: local include-minor-version = YES ; switch $(toolset) { case borland* : toolset-tag += bcb ; case como* : toolset-tag += como ; case cwpro8* : toolset-tag += cw 8 ; case cwpro9* : toolset-tag += cw 9 ; case cw-* : toolset-tag += cw ; include-minor-version = ; case darwin* : toolset-tag += ; case edg* : toolset-tag += edg ; case gcc* : toolset-tag += gcc ; case intel-linux* : toolset-tag += il ; case intel-win32* : toolset-tag += iw ; case kcc* : toolset-tag += kcc ; case kylix* : toolset-tag += bck ; case metrowerks* : toolset-tag += cw ; case mingw* : toolset-tag += mgw ; case mipspro* : toolset-tag += mp ; case msvc* : toolset-tag += vc 6 ; case sunpro* : toolset-tag += sw ; case tru64cxx* : toolset-tag += tru ; case vacpp* : toolset-tag += xlc ; case vc[678][_]* : { toolset-tag += vc ; toolset-tag += [ MATCH "vc([678])[_]([0123456789]*)" : $(toolset) ] ; } case vc[678]* : { toolset-tag += vc ; toolset-tag += [ MATCH "vc([678])" : $(toolset) ] ; } case * : toolset-tag += [ MATCH "^([^-]*)" : $(toolset) ] ; } if $(include-minor-version) { toolset-tag += [ MATCH "[-]([0123456789]+)[_.]([0123456789]*)" : $(toolset) ] ; } else { toolset-tag += [ MATCH "[-]([0123456789]+)[_.][0123456789]*" : $(toolset) ] ; } which does not match autolink expectations for the following toolsets adhering to the new naming conventions: vc-6_5 --> vc65 (expected vc6) vc-7_0 --> vc70 (expected v7) I guess it suffices to apply the following postrule in boost-base.jam switch $(toolset-tag) { case vc6* : toolset-tag = vc6 ; case vc70 : toolset-tag = vc7 ; } but someone more acquainted with bjam than me might come up with a nicer reformulation. Currently, this is breaking dozens of tests in the metacomm engine, which recently switched to vc-6_5-stlport and vc-7_0 toolsets. Do I commit this? Someone can tackle the issue more elegantly? Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

meta-double
by Peder Holt 13 Jun '05

13 Jun '05

Is there any interest in a compile-time meta-version of double? Syntax: //Definition typedef META_DOUBLE(3.1415926535897932384626433) pi; //Or META_DOUBLE(3.1415926535897932384626433) pi_; //Mathematical operations typedef math::meta::add<pi,pi>::type pi2; //Evaluation: assert(META_DOUBLE_EVAL(pi2)==3.1415926535897932384626433*2); This implementation uses two ints to represent the decimals, and a short to represent the exponent. It has been tested on VC7.1,VC8.0 beta and GCC3.2 Regards, Peder

8 27

msvc-tools
by Victor A. Wagner Jr. 13 Jun '05

13 Jun '05

I changed the /EHsc to /EHac which seems to affect none of the tests excep the errors test on VC-8_0 which now works I've tested it with 7.1 and 8.0 I don't have any other complers btw, why is the /EHac (now) put in the command line twice? once as part of CFLAGS and once directly?? I just started another regression test....I'll be back before it finishes Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

2 1

logging library - minor bug report in "$yy" year formating
by Andy Schweitzer 13 Jun '05

13 Jun '05

Hello there, been playing with the logging library. Is this the right place to post bug reports? It seems that $yy prints "105" for the year 2005, not "05", which I expected. $yyyy is correct, it prints 2005. If line 173, // vals[m_yy + 1] = details.tm_year; is changed to // vals[m_yy + 1] = details.tm_year % 100; it appears to work... although I only tested with today's date.

2 1

logging library - v1.3.3
by John Torjo 13 Jun '05

13 Jun '05

Hi all, Just included the nifty appenders from Caleb, and made some small fixes. Enjoy! http://torjo.com/code/logging-v133.zip Best, John -- John Torjo, Contributing editor, C/C++ Users Journal -- "Win32 GUI Generics" -- generics & GUI do mix, after all -- http://www.torjo.com/win32gui/ -v1.6.3 (Resource Splitter) -- http://www.torjo.com/cb/ - Click, Build, Run!

2 2

IR is using boost
by Andrew Cameron 13 Jun '05

13 Jun '05

Name: PROGNOSIS IP Telephony Manager IP Telephony Express Company: Integrated Research P/L Description: PROGNOSIS is a suite of IP telephony management software products, specifically designed to address the key challenges of IP telephony life cycle management, including network-readiness, assessment, pre-deployment assurance testing, and ongoing Day-2 management of Cisco CallManager, Cisco Unity, and Cisco AVVID infrastructure. Boost Libs: boost.any boost.bind boost.function boost.lexical_cast boost.mpl boost.numeric_cast boost.ref boost.regex boost.smart_ptr boost.thread boost.thread_pool boost.type_traits URL: http://www.ir.com _____________________________________________________________________ This email is intended only for the use of the individual or entity named above and may contain information that is confidential and/or privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this Email in error, please notify us immediately by return email or telephone +61 2 9966 1066 and destroy the original message. Thank You _______________________________________________________________________

1 0

Help setting up boost for vc7
by Chris Ward 13 Jun '05

13 Jun '05

I have MS VC++ 7.1 installed to the default location (C:\Program Files\Microsoft Visual Studio .NET 2003), O/S WinXPSP2 However, when I run Build.bat from the command line, it returns " \Utilities\Bin\x86 was unexpected at this time." This occurs if I let the script auto-detect and also if I specify the toolset as vc7. Can someone please steer me in the right direction? regards Chris Ward

3 2