- Boost - lists.preview.boost.org

[serialize] xml archives and versioning
by Russell Hind 25 Oct '04

25 Oct '04

The header of our xml archive looks like this: <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <!DOCTYPE boost_serialization> <boost_serialization signature="serialization::archive" version="3"> <CoatingScanConfig class_id="0" tracking_level="0"> The object written as CoatingScanConfig didn't have a class version specified (and therefore there isn't one in the header). When writting this class, the version parameter is passed in to the serialize() method is 0 for the class, but when reading it, the version number is subsequently passed in as 3 (which looks like the archive version). Should it not be 0 also? Is 0 a valid version number for a class? If I specify the class version as 1, then reading and writing both get '1' as the version, but if I don't specify a version, or I specify 0, then writing gets 0, but reading gets '3'. If 0 isn't valid, then could there be a static_assert catching this? And a quick usage question: If a class isn't versioned, is an inherent 'version 0' written to the archive so that a version number of 1 can be applied to the object later when it is modified, or do objects need to be given a version number from the start? Thanks Russell

2 9

[Test] Linking problems
by David B. Held 25 Oct '04

25 Oct '04

unit_test_log.o: In function `boost::unit_test::unit_test_log::unit_test_log()': unit_test_log.o(.text+0x17e): undefined reference to `boost::unit_test::ut_detai l::msvc65_like_log_formatter::msvc65_like_log_formatter(boost::unit_test::unit_t est_log const&)' unit_test_log.o: In function `boost::unit_test::unit_test_log::unit_test_log()': unit_test_log.o(.text+0x270): undefined reference to `boost::unit_test::ut_detai l::msvc65_like_log_formatter::msvc65_like_log_formatter(boost::unit_test::unit_t est_log const&)' unit_test_log.o: In function `boost::unit_test::unit_test_log::set_log_format(bo ost::unit_test::basic_cstring<char const>)': unit_test_log.o(.text+0x1000): undefined reference to `boost::unit_test::ut_deta il::msvc65_like_log_formatter::msvc65_like_log_formatter(boost::unit_test::unit_ test_log const&)' unit_test_log.o(.text+0x1056): undefined reference to `boost::unit_test::ut_deta il::xml_log_formatter::xml_log_formatter(boost::unit_test::unit_test_log const&) ' This is from the latest CVS update. Any idea how to fix it? Dave

3 3

RE: [boost] about the "latest news" section [was ATTN: Branch forrelease is scheduled for tonight]
by Brian Braatz 25 Oct '04

25 Oct '04

I would like to also re-submit my request for a spot on the boost main page which has the target for when the next version will be "out". (I am anxiously waiting 1.32) > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Joaquín Mª López Muñoz > Sent: Tuesday, October 19, 2004 8:26 AM > To: boost(a)lists.boost.org > Subject: [boost] about the "latest news" section [was ATTN: Branch > forrelease is scheduled for tonight] > > Aleksey Gurtovoy ha escrito: > > > I'll post another notice right before the branching, and yet > > another one when it's complete. > > > > Regarding the "latest news" section on the main page: > > 1. Shouldn't we adopt the subsection layout as in Boost 1.31, > with "New Libraries", "Updated Libraries", etc.? > 2. Numeric Conversion does not appear listed, yet it is a newly > added library (it shows, though, in the libs page.) > 3. Same for Minmax. > 4. A bio for Herve Bronnimann is uploaded in boost/people, but > it is not linked from boost/people/people.htm. > > I volunteer to take care of this stuff, if no one objects. > > 5. Missing pictures for Fernando Caccional and Hervé. > > Joaquín M López Muñoz > Telefónica, Investigación y Desarrollo >

2 1

[boost][MPL] Numeric metafunctions protocol/infrastructure
by Cromwell Enage 24 Oct '04

24 Oct '04

Once Tropical Storm Jeanne passes away, I should be through with hurricanes for a while. The latest-and-greatest MPL looks great! The new ability to plug in custom numeric metatypes so that they work with existing numeric ops makes it a definite keeper. The part of my sub-library that I've updated to work with the new MPL is at <http://groups.yahoo.com/group/boost/files/mpl_math.zip>, and has been tested with MinGW 3.2 and MSVC 7.1 (2003 Toolkit). Renaming issues aren't too bad; I just have to remember (for one thing) that reverse_copy is defined at copy.hpp and not reverse_copy.hpp as I originally thought. I also noticed that BOOST_MPL_AUX_TYPEOF is no longer there, but I've managed to eliminate the need for it. A major issue I have is how to properly use numeric_cast in order to make something like the following statement work correctly: typedef plus<int_<1>,fraction_c<long,4,3> >::type fraction_7_over_3; Right now I've made N^2 specializations of plus_impl, where N here means the total number of built-in and custom numeric metatypes. For my sub-library, N==4, which means I've made 16 specializations of plus_impl alone! Factor in the comparison ops as well the arithmetic ops, and my code is starting to look bloated. I've supplied a couple of convenience macros to reduce the copy-and-pasting, but I still think I'm missing something crucial here, and I think that something is how to use (or specialize) numeric_cast. Pointers welcome! Cromwell Enage __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail

2 6

[MPL] eval_if<> woes
by David B. Held 23 Oct '04

23 Oct '04

I'm getting weird errors from gcc-3.4.2 saying that eval_if<> does not have a nested 'type'. I just did a CVS update. Any clues, or do I need to provide more context? Dave

3 4

[bind] and overloading function
by Alexey Nikitin 23 Oct '04

23 Oct '04

Is it possible (exist way) to give instructions to functions boost::bind or boost::lambda::bind which from overloading functions I need to pass?

3 3

bit of singed integer and proposoal
by I.J.Wang 23 Oct '04

23 Oct '04

Hi: I have recently written a C++ library, it is hoped as the most bottom level of C++ functions. Many issues might be interested there. http://freshmeat.net/projects/libwx http://sourceforge.net/projects/libwx There are so many incompatible issues with the standard practice. I would like to know about your ideas. 1. The most fundamental thing is about the returning mechanism. It involves the return type and exception type. Please download file libwy-0.15.tgz at least to see README.TXT to understand. 2. About the definition of bit with number (it is very attractive in theory). Is it practical to define the bit of number with signed types? because my implementation would require the machine always use MSB as the sign bit for integer types. 3. This is about the class member naming convention: (ripped from README.TXT) It is so far stable, I would like to propose for boost I know there are incompatibles, but think it as 'lowest level' might solve these problems. -- Let T denote a given class of this library . The following member names and associated functionalities are defined. T() default constructor. The object thus constructed is referred to as in default state and so the default object. If object can mean 'no instance', or be unbound state etc., the default object is better thus designed. Exception postcondition: object does not exist reset(...) Reconstruct the object to the state as constructed. If reset(...) defined, there exists the argument corresponding constructor (reset() usually exists) Note: reset() should always leave an default object, whatever an error is reported, either by return or by throwing exception ~T Destruct and discard object Postcondition: object does not exist bool is_default() const return true iff object is equivalent to the default constructed object (i.e a.is_default() <==> a==T()) bool operator==(const T& r) const This function returns true iff *this and r are not distinguishable by using any non-private member on the same condition unless otherwise specified. All the returned objects or that may be modified by the other members of T should have their operator==(const T&r) defined to prove the defined equivalence. Note: Address and SLI are not objects' own property operator=(const T&) Assign/reconstruct object to the state as the copy constructor constructed. The assigned object should be deterministic by the argument (i.e. f=x and g=x imply f==g). A function of such functionality should however be defined. For using expressions might otherwise be analysed to ambiguity and the future use is very likely of exponential complexity Fault return-type exception class derived from WyRet. _.. prefix for system-specific members or candidate, or restricted

1 0

[variant] regressions in gcc-2.95.3-linux and gcc-2.95.3-stlport-4.5.3-linux
by JOAQUIN LOPEZ MU?Z 23 Oct '04

23 Oct '04

Hi all, Just wanted to record the following, in case it can be helpful for someone to solve the current regressions of variant for the mentioned toolsets: Latest regression runs before branching also failed for GCC 2.95.3, but *only* in the second toolset. That is, gcc-2.95.3-linux was working fine. Given that I'm pretty sure none of the relevant code (MPL or variant code itself) has changed since, I'd say this could have to do with some local change on Martin Wille's environment during the branching. Maybe the toolset rules? HTH Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

RE: [boost] Re: SOCI db lib [Was: RTL status -"help wanted"]
by Brian Braatz 22 Oct '04

22 Oct '04

> -----Original Message----- > Subject: Re: [boost] Re: SOCI db lib [Was: RTL status -"help wanted"] > > On Wed, 20 Oct 2004 00:15:52 -0500, David B. Held wrote > > Steve Hutton wrote: > > > [...] > > > So the relevance of ODBC is open to debate - the key IMHO is uniform > > > support for all the major databases. ODBC may be a quick means to > > > that end. Native drivers can always be added later, or vise-versa. > > Agree. > > > In my experience, ODBC can be unbelievably slow, also. It is definitely > > not a cure-all. It should probably be supported, but creating an > > interface that will elegantly support native drivers should be a > > priority. > Jeff Garland: > Sure having good support for native drivers is fine, but I think it is > much, > much, harder to achieve. So my push for ODBC binding is primarily to meet > the > 'all major databases' supported quickly. > > Jeff [Brian Braatz] >From a practical point of view, I believe Jeff to be 100% right here. I have been searching for a good solution for this, and the odbc \ unixodbc path gets a framework up and running quickly. I would add that it would be nice to have that framework support "unplugging" the odbc aspect and placing in native or other drivers later. I view this perspective as the scaffolding that supports the statue, while the statue is being carved :)

1 0

[serialization] and arrays with bcc32
by Russell Hind 22 Oct '04

22 Oct '04

I'm trying to serialise arrays (boost::array, actually). There aren't any specific headers for it as there are for STL types. Could one be added at some point? But I've run in to a more basic compilation problem under bcc32: This won't compile #include <boost/archive/text_oarchive.hpp> double d[3]; d[0] = 0.0; d[1] = 1.0; d[2] = 2.0; std::ofstream ofs("c:\\test.txt"); archive::text_oarchive toa(ofs); toa & d; The error I get is [C++ Error] interface_oarchive.hpp(105): E2031 Cannot cast from 'double *' to 'double ( &) const[3]' Is this a problem with Borland or is my syntax for serialising arrays? Thanks Russell

3 3