- Boost - lists.boost.org

problem with building Boost version 1_34_1
by Oliver Kullmann 28 Jan '09

28 Jan '09

Hello, I have some "legacy code" to compile, using Boost version 1_34_1. The compiler is gcc 4.1.2 (new versions of Boost don't work anymore, and neither newer versions of gcc). It used to go through, but now on 64-bit platforms I get the following build error: In file included from ./boost/spirit/attribute/closure.hpp:24, from ./boost/wave/grammars/cpp_expression_grammar.hpp:16, from libs/wave/src/instantiate_cpp_exprgrammar.cpp:21: ./boost/spirit/phoenix/operators.hpp:355: error: ‘INT_MAX’ was not declared in this scope Now looking into the code that' correct (INT_MAX seems not be declared somewhere). (BTW, there are many other errors like that; that's just the first one.) So, apparently, somehow INT_MAX used to "slip in" by some uncontrolled inclusion, and now this is no longer the case. But what I don't understand: I always compiled it with the same local installation of gcc (4.1.2)? So I guess it is due to a newer version of glibc now installed? So I need to install first an old version of glibc (which?), then make gcc aware of it (?), and then build boost? I would be glad for some help (hints)! Oliver

2 1

Calling for 1.38 news items / library changes and additions.
by John Maddock 28 Jan '09

28 Jan '09

Just a quick reminder to everyone that since the 1.38 release is now in progress we're looking for items to go in the news/what's new section of the 1.38 release notes. Items should be added to the quickbook file website/public_html/beta/feed/history/boost_1_38_0.qbk, then cd into website/public_html/beta and run bjam. If there are no errors then commit (should be 3 changed files) and check the result looks OK at http://beta.boost.org/users/news/version_1_38_0. If there are any problems then please post the content in reply to this message. Regards, John Maddock.

3 3

Two minor (?) legal-related questions (empty lines and "Boost sponsorship")
by Gennaro Prota 28 Jan '09

28 Jan '09

Hi guys, the "how to apply to source files" entry at <http://www.boost.org/users/license.html> asks to leave an empty line before and after the comment block which contains copyright notice and license reference. I'm wondering if that was an advice from the lawyers who wrote the license or just a stylistic preference. Also, I just saw a BoostSponsorshipAgreement.pdf in the more/ subdirectory. What is it? -- Genny

5 4

[1.38.0] beta release candidate
by Beman Dawes 28 Jan '09

28 Jan '09

[1.38.0] beta release candidate packages are available at http://boost.cowic.de/rc/ I'm doing a library build right now on Windows/VC++ 9.0. I'd appreciate it if someone could try a library build on a Linux system, and report any problems. Although we won't hold the beta for minor tweaks, I would like to be sure that docs are present and libraries build before pushing this out to SourceForge. Thanks, --Beman

7 14

[serialization] serializing tr1::unordered_map
by Kenny Riddile 28 Jan '09

28 Jan '09

Just wondering if a tr1::unordered_map can be serialized yet, whether it be via the released version of the library or via some extension. I remember some discussion about it back in 2007, but I didn't have a need for it then, so I didn't follow the discussion. Thanks, Kenny Riddile

2 1

[regex] [1.35]Problem with IPV6 validation windows XP
by Gopal_Haldar＠McAfee.com 28 Jan '09

28 Jan '09

I am using same expression for .net application and javascript it is working fine but when I used for boost regular expression the following problem is facing But it is failed to validate foramt like 2001:470:1f01:115::1 or 2001::11 or 2001:1::11 Please see my code... bool IsValidIPv6String(wstring ipv6address) { wsmatch what; wregex expression(L"^((([0-9A-Fa-f]{1,4}:){7}[0-9A-Fa-f]{1,4})|(([0-9A-Fa-f]{1, 4}:){6}:[0-9A-Fa-f]{1,4})|(([0-9A-Fa-f]{1,4}:){5}:([0-9A-Fa-f]{1,4}:)?[0 -9A-Fa-f]{1,4})|(([0-9A-Fa-f]{1,4}:){4}:([0-9A-Fa-f]{1,4}:){0,2}[0-9A-Fa -f]{1,4})|(([0-9A-Fa-f]{1,4}:){3}:([0-9A-Fa-f]{1,4}:){0,3}[0-9A-Fa-f]{1, 4})|(([0-9A-Fa-f]{1,4}:){2}:([0-9A-Fa-f]{1,4}:){0,4}[0-9A-Fa-f]{1,4})|(( [0-9A-Fa-f]{1,4}:){6}((\\b((25[0-5])|(1\\d{2})|(2[0-4]\\d)|(\\d{1,2}))\\ b)\\.){3}(\\b((25[0-5])|(1\\d{2})|(2[0-4]\\d)|(\\d{1,2}))\\b))|(([0-9A-F a-f]{1,4}:){0,5}:((\\b((25[0-5])|(1\\d{2})|(2[0-4]\\d)|(\\d{1,2}))\\b)\\ .){3}(\\b((25[0-5])|(1\\d{2})|(2[0-4]\\d)|(\\d{1,2}))\\b))|(::([0-9A-Fa- f]{1,4}:){0,5}((\\b((25[0-5])|(1\\d{2})|(2[0-4]\\d)|(\\d{1,2}))\\b)\\.){ 3}(\\b((25[0-5])|(1\\d{2})|(2[0-4]\\d)|(\\d{1,2}))\\b))|(([0-9A-Fa-f]{1, 4}:){0,5}::([0-9A-Fa-f]{1,4}:){0,5}[0-9A-Fa-f]{1,4})|(::([0-9A-Fa-f]{1,4 }:){0,6}[0-9A-Fa-f]{1,4})|(([0-9A-Fa-f]{1,4}:){1,7}:))$"); Please look into the expression. Regards Gopal

1 0

[1.38] Generating README.txt
by Daniel James 28 Jan '09

28 Jan '09

Hi Beman, Cmake needs a README.txt file based on the release notes. There's an out of date one in trunk, but nothing in the release branch. We generate this fairly easily using the lynx browser: lynx -dump -nolist -display_charset=utf-8 \ http://beta.boost.org/users/history/minimal.php/version_1_38_0 \ > README.txt It's probably easiest for you to add this to your release scripts, but if you prefer I could do it when generating the documentation, and upload the README.txt file and you could then copy it into place. Daniel

2 2

to_utf8/from_utf8
by Goran Mitrovic 27 Jan '09

27 Jan '09

It would be nice if boost would export and document to_utf8 and from_utf8 functions (possibly from string utils *headers only* library). Currently, I use following workaround, but I believe those two useful utility functions deserve better: #define BOOST_PROGRAM_OPTIONS_NO_LIB 1 #include <boost/program_options/detail/convert.hpp> #include <boost/program_options/detail/utf8_codecvt_facet.hpp> #undef BOOST_PROGRAM_OPTIONS_NO_LIB #include <libs/program_options/src/convert.cpp> #include <libs/program_options/src/utf8_codecvt_facet.cpp>

1 0

[1.38.0] [Getting started] Windows example boo boo?
by Beman Dawes 27 Jan '09

27 Jan '09

In the Windows example in section 5.4.2, C:\WINDOWS> cd C:\Program Files\boost\boost_1_38_0 C:\Program Files\boost\boost_1_38_0> bjam ^ More? --build-dir="C:\Documents and Settings\dave\build-boost" ^ More? --toolset= --build-type=complete msvc stage Shouldn't "msvc" follow "--toolset="? --Beman

2 3

[format] Inconsistencies with printf
by Sam Partington 27 Jan '09

27 Jan '09

Hi, There are still several differences between printf and Boost.Format : http://www.boost.org/doc/libs/1_37_0/libs/format/doc/format.html#printf_dif… Whilst I realise that it is difficult to fully meet the printf formats, is there likely to be an improvement in this area? We are using Boost.Format to replace a lot of existing sprintfs, so having exact compatiblitity would be very useful. At the least it would be nice if unsupported options were ignored silently. For example we had the format string "%8.8x" silently pad the result with spaces rather than zeros, which rather surprised us, as we have all exceptions switched enabled. I have managed to add a rather poor emulation of the precision with integral types. It only works correctly when the width and the precision are the same, but at least it will raise an exception in other cases, and if exceptions are disabled it prefers to pad with zeros as that breaks our code less. I realise that others mileage may vary. But for myself I prefer this non-silent version. i.e. : "%8.8x" % 0x1234 == 00001234 "%8.3x" % 0x1234 == 00001234 * "%3.8x" % 0x1234 == 00001234 * sprintf would return " 1234" here. parsing.hpp:267 : In function parse_printf_directive just before the switch on the type char. // begin SRP added if(precision_set && strchr("xXpoudi", int(wrap_narrow(fac, *start, 0)))) { if (fpar->fmtstate_.precision_ != fpar->fmtstate_.width_) { // we only support the precision on integral types if the width and // the precision are identical. If exceptions are enabled then // throw, but if not do something vaguely sensible, and pad with // zeros up to the largest width specified maybe_throw_exception(exceptions, start-start0+offset, fstring_size); if (fpar->fmtstate_.precision_ > fpar->fmtstate_.width_) { fpar->fmtstate_.width_ = fpar->fmtstate_.precision_; } } fpar->pad_scheme_ |= format_item_t::zeropad; } // end SRP added One of the goals of the Format library is to "provide printf-compatibility, as much as it makes sense in a type-safe and type-extendable context." Is this goal still valid? Sam

1 0