- Boost-users - lists.boost.org

Compile errors with format.hpp on AIX
by Rich Cook 26 Aug '05

26 Aug '05

Hi, Sorry for this repost; my first post was ignored or didn't make it to the list somehow. I am hoping the answer is not, "Forget it, boost doesn't work on AIX." But that is what I'm beginning to suspect. Or am I posting to the wrong list? Including boost/format.hpp on AIX in my project results in the following errors. Does anyone have an idea what is happening? I googled all over the place but found no help on the subject. Is boost only good with gcc? I don't think so, because the compiler for boost works with xlC. Hmm. xlC -c -g -I/g/g0/rcook/aix_5_64_fed/include -I/g/g0/rcook/ downloads/boost_1_33_0 MirandaReader.C -o aix_5_64_fed/MirandaReader.o "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 388.66: 1540-0217 (S) "T" is not a member of "locale". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 388.10: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::locale>::destroy_impl (is_not_reference_tag)". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 362.9: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::locale>::destroy()". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 208.24: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::locale>::~optional_base()". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 130.7: 1540-0700 (I) The previous message was produced while processing "boost::optional_detail::optional_base<std::locale>::__dftbdt()". "/g/g0/rcook/downloads/boost_1_33_0/boost/optional/optional.hpp", line 471.5: 1540-0700 (I) The previous message was produced while processing "boost::optional<std::locale>::~optional()". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/internals.hpp", line 38.9: 1540-0700 (I) The previous message was produced while processing "boost::io::detail::stream_format_state<char,std::char_traits<char> >::stream_format_state(char)". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/internals.hpp", line 78.53: 1540-0700 (I) The previous message was produced while processing "boost::io::detail::format_item<char,std::char_traits<char>,std::allocat or<char> >::format_item(char)". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/ format_implementation.hpp", line 121.40: 1540-0700 (I) The previous message was produced while processing "boost::basic_format<char,std::char_traits<char>,std::allocator<char> >::make_or_reuse_data(size_t)". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/parsing.hpp", line 415.9: 1540-0700 (I) The previous message was produced while processing "boost::basic_format<char,std::char_traits<char>,std::allocator<char> >::parse(const string_type &)". "/g/g0/rcook/downloads/boost_1_33_0/boost/format/ format_implementation.hpp", line 64.9: 1540-0700 (I) The previous message was produced while processing "boost::basic_format<char,std::char_traits<char>,std::allocator<char> >::basic_format(const string_type &)". "MirandaReader.C", line 138.6: 1540-0700 (I) The previous message was produced while processing "MirandaDataSet::GetGridOrigin(long, Point<double> &)". gmake: *** [aix_5_64_fed/MirandaReader.o] Error 1 -- Richard Cook ✇ Lawrence Livermore National Laboratory Bldg-453 Rm-4037, Mail Stop L-557 7000 East Avenue, Livermore, CA, 94550, USA ☎ (925) 423-9605  (925) 423-6961 --- Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept. (opinions expressed herein are mine and not those of LLNL)

1 0

Minor refinements for boost::rational
by Daniel Krügler 26 Aug '05

26 Aug '05

Hello, After a short view at the rational.hpp header I propose to perform the following changes: 1) As counterpart to the existing: bool operator!() const; one should definitly add: operator bool_replacement_type() const; with a proper (member function pointer) definition of bool_replacement_type. 2) The function template template <typename IntType> IntType lcm(IntType n, IntType m); should be defined as template <typename IntType> IntType lcm(IntType n, boost::call_traits<IntType>::param_type m); which makes sense in this case because m is not modified internally (in contrast to n) 3) The boost::rational IO should use proper templated extractors and inserters for those (most) compilers, which provide corresponding std IO libraries, such that #if defined (BOOST_NO_TEMPLATED_STREAMS) ... // current impl #else template<class CharType, class CharTrait, class IntType> inline std::basic_istream<CharType, CharTrait>& operator>>(std::basic_istream<CharType, CharTrait> &is, rational<IntType>&); template<class CharType, class CharTrait, class IntType> inline std::basic_ostream<CharType, CharTrait>& operator<<(std::basic_ostream<CharType, CharTrait> &os, const rational<IntType>&); #end Furtheron I propose to replace the helper class detail::resetter by boost::ios_flags_saver, or even better to remove it all all, because I assume, that the temporary unsetting of the skipws flag does not make much sense - Does it? I also propose to replace the current setting of ios_base::badbit (if widen('/') was not found) by the more appropriate setting of ios_base::failbit - This behaviour is in sync with std::complex and boost::tuple! Greetings from Bremen, Daniel Krügler

3 10

MPL and conditional compilation
by Alan M. Carroll 26 Aug '05

26 Aug '05

2 1

Regex Lib: Feature Set: Newbie ?
by Jordanna Chord 26 Aug '05

26 Aug '05

Newbie question; I'm porting a project from PCRE 3.9 to the most recent version of Boost Regex++. Has anyone compiled a list of differences between the regex supported by Boost and other libraries such as PCRE which supports Perl 5? Thanks, Lacey

2 1

Boost.Random: Suspicious code in uniform_smallint_integer
by Daniel Krügler 26 Aug '05

26 Aug '05

Although uniform_smallint_integer currently is no official code (its in the details section and seems nowhere used), I would like to mention, that the current implementation contains a subtle bug: The member _factor is never initialized, thus calling operator()() would cause U.B. The reason is, that the initializer member function set defines a **local** variable _factor, which is never assigned to this->_factor, such that uniform_smallint_integer::_factor will never be assigned. Just one question: Is detail::uniform_smallint_integer a leftover of some experiments by the library responsible or does it exist for interested boost users to test it? Greetings from Bremen, Daniel

1 0

Re: [Boost-users] Boost serialization
by Li Lirong 26 Aug '05

26 Aug '05

You may try to serialize the data to a std::vector. See here for how to write a ostream with std::vector: http://www.boost.org/libs/iostreams/doc/tutorial/container_sink.html Regards, Lirong --- Srikanth Rao <srirao_us(a)yahoo.com> wrote: > Hi, > > I saw a mail from you to the group. I have a similar > issue but I need to send the serialized data on the > network. > > After serializing to a stream, can I get the buffer? > > How? > TIA, > Sri. > > > > __________________________________ > Yahoo! Mail for Mobile > Take Yahoo! Mail with you! Check email on your > mobile phone. > http://mobile.yahoo.com/learn/mail > __________________________________ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250

1 0

Re: [Boost-users] Boost.Thread memory leak reported
by Sohail Somani 25 Aug '05

25 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Elisha Berns > Sent: Wednesday, August 24, 2005 8:48 PM > To: Boost > Subject: [Boost-users] Boost.Thread memory leak reported > > > > Detected memory leaks! > Dumping objects -> > {146} normal block at 0x00227008, 24 bytes long. > Data: < | > 08 7C 04 00 FF FF FF FF 00 00 00 00 00 00 00 > 00 > {145} normal block at 0x00223928, 8 bytes long. > Data: < p" > 08 70 22 00 01 CD CD CD > Object dump complete. Hi Elisha, Could you come up with a small test case that demonstrates the problem?

4 7

Re: [Boost-users] Boost.Thread memory leak reported
by Sohail Somani 25 Aug '05

25 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Christian Henning > Sent: Thursday, August 25, 2005 4:03 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Boost.Thread memory leak reported > > > I'm just wondering why Purify doesn't show anything. (it sucks) Disclaimer: I only used it enough to make the above statement

1 0

[Test] redirecting unit test report
by Kim Barrett 25 Aug '05

25 Aug '05

I'm using the unit test framework provided by Boost.Test, mostly using the auto unit test facility. I wrote a parser for the XML formatted report output, as part of a regression package. Unfortunately, changes between 1.32 and 1.33 are causing a problem. The format of the XML output changed quite a bit between 1.32 and 1.33. Ok, I can deal with that; in fact, the new format is quite a bit easier to deal with, and I've already finished with the changes. It would be nice if this format were documented though. Unfortunately, there is one change that I haven't been able to figure out a good way to deal with. If a test case aborts, due to an exception uncaught by the test itself, the exception is caught by the unit test framework. The occurrence of the abort is recorded in the test results. In 1.32, this would be reported by including an <aborted ...> subentry for the test case data, including some descriptive text. In 1.33, the descriptive text is printed to std::cerr and the report indicates that the test case was aborted via the "result" value for the test case. The generated report no longer contains the descriptive text. (I don't care all that much about this last change.) The problem is the printing of the descriptive text for the exception to std::cerr. That is also the stream to which the test report is written, and I'm capturing the report information by redirecting stderr to a file when invoking a test program. The exception text ends up appearing at the beginning of the report file, and isn't valid XML, which causes my report parser to die. (If necessary, I may end up prefixing the parser with a step to skip over anything that doesn't look like XML, but that's pretty ugly.) Now, I never really liked redirecting stderr to a file in order to capture the report. What if something in the test program were to write to stderr? (Which is exactly what is happening now.) I see that there is now (in 1.33) a mechanism for setting the stream used by the report generator (boost:unit_test::results_reporter::set_stream()). But after spending the last couple of days pouring over the documentation and sources for Boost.Test, I have no idea where I would put a call to that function that doesn't involve patching the Boost.Test sources. There doesn't seem to be a place to insert such user code, at least not that I can find. Have I overlooked something, or is this really a hole in the present design / implementation?

3 13

Intermittent problem(s) building boost 1.33 with VC7.1
by Elisha Berns 25 Aug '05

25 Aug '05

The message "failed to write command file" comes up intermittently and seemingly at random when I build some or all of the 1.33 libraries. Once that message appears the build is killed and that's it. So far I have only been able to build the thread and iostreams libraries. What's the deal? Is it some problem with my machine, or with the build itself? Thanks, Elisha Berns e.berns(a)computer.org tel. (310) 556 - 8332 fax (310) 556 - 2839

2 1