- Boost - lists.preview.boost.org

autoconf-like configure on RC_1_33_0 branch
by Doug Gregor 05 Nov '05

05 Nov '05

I've placed an autoconf-like "configure" script on the RC_1_33_0 branch. If you're a *nix user and would like an alternative to directly using bjam, give it a try and send me some bug reports :) Typically one would just use: ./configure --prefix=/where/to/install make make install Run "./configure --help" for more options. Cheers, Doug

9 13

Documentation Wizard
by Rob Stewart 05 Nov '05

05 Nov '05

Quite some time ago, Dave Abrahams announced that I was the new Boost Documentation Wizard. I said I'd write something on the subject and that is long overdue. Herewith, I describe what I think the DocWiz should do and what is needed from volunteers to make it happen. That is, I'm trying to document the new DocWiz role and solicit your help. Please have a look and comment on what I'm proposing. If you don't like the direction I'm planning, say so. If you think I've missed something, let me know. If you think you can help in some way, please let me know; I can't do the job alone. The DocWiz's purpose is to try to foster better documentation for Boost. Since this is something new at Boost, some measures will be grandfathered* of necessity, while others will likely be retrofitted to existing documentation. Some things will be purely stylistic, but most will be substantive. A significant problem with writing library documentation is that English is often not the library author's primary language.* It is all too common that those who can write C++ fluently cannot write English well. Thus, we need a means to ensure that the library author's ideas are well communicated. Another problem with writing library documentation is knowing what to write. How much detail is sufficient? How many code examples should there be? How much material should be relegated to a reference section and how much should be presented in a tutorial? What is a sufficient rationale for the library? Many of these issues can be addressed by seeking insight from what has been written well already and by seeking advice from those expert on the tasks. From that information we can capture best practices to assist new documentation authors. Still another problem is consistency. As Boost grows, having a reasonably consistent look and feel to our documentation becomes increasingly important. Naming and organizing sections in our documentation must be consistent across libraries to simplify locating desired information in each library. Given the rate at which new libraries are proposed, I cannot do this task alone. I'm the father of eight (yes, 8!) children (so far, at least), I have a full time job, etc. Like everyone else, I'm quite busy. Thus, I need help. I intend to be the manager of a group of folks who can divide the workload to make it manageable. To that end, I propose the following positions to assist in improving the state of Boost documentation: Editors - Folks with demonstrably good English skills who can assist library authors by clarifying and correcting the documentation at various times, as determined by the author, so the meaning is clear. Editors also advice the author on structural changes necessary to conform to Boost guidelines. Editors are not so much concerned with content as with clear communication of what is included. Domain Experts*** - Folks with special skills in writing certain types of documentation such as concepts or tutorials; when a library author is struggling to write a portion of the library's documentation, the author can call upon the appropriate domain expert for assistance. Mentors - Folks with skills and desire to write good documentation who can come alongside a new library author to ghost write, share writing tasks, suggest content, etc. The output from author/mentor collaboration must still be approved by an editor. The workload of an editor will be varied since the number of authors writing documentation varies and based upon their update schedules. The workload of a domain expert should be quite low as folks writing concept descriptions, for example, should not need a domain expert's input often or long. The workload of a mentor likely will be as high as the mentor wishes. Initially, anyone acting as an editor will need to prove his/her skills by relying on trusted editors to proof the results. Once proven, a new editor can act autonomously. The expected result of this group of folks is documentation that is acceptable to Boost. I propose that a library cannot be fully accepted by Boost without the DocWiz's approval. IOW, a library can be conditionally accepted pending documentation approval. (That approval may be given based solely upon the word of a trusted editor; the DocWiz needn't read every document to give approval, but the responsibility does lie with the DocWiz for deficient approved documentation.) Note that the DocWiz is not the final authority on what is acceptable documentation. Users of that documentation are. An author will likely need to update documentation based upon user experience. Such changes should be subject to an editorial review, too, in order to maintain high standards. -------- * That means that existing documentation needn't be changed to conform to new policies, but may be if the author chooses. ** Another problem is that English *is* the library author's primary language. :) *** The name "domain expert" smacks too much of someone who is expert in the domain of the library rather than of a particular aspect of library documentation. Please suggest a better name. -- Rob Stewart stewart(a)sig.com Software Engineer http://www.sig.com Susquehanna International Group, LLP using std::disclaimer;

6 6

Re: [boost] [ANN] Phoenix-2 prerelease
by David Abrahams 05 Nov '05

05 Nov '05

Joel de Guzman <joel(a)boost-consulting.com> writes: > Comments, feedback very welcome! > Organization > > Care and attention to detail was given, painstakingly, to the design > and implementation of Phoenix. The overall design of the library is > well structured and clean. Remarks like the last one usually cause me to be more suspicious of, than confident in, a library design. I suggest you strike it. > The library is organized in four layers: > > The modules are completely orthogonal. I'm not sure what that means. If you're going to say it, you should explain it. > The relationship between the > layers is totally acyclic. "The modules are orthogonal, with no cyclic dependencies" http://www.asne.org/index.cfm?ID=4364 > Lower layers do not depend nor know the > existence of higher layers. "Lower layers do not depend on higher layers." http://www.asne.org/index.cfm?ID=4364 > Modules in a layer do not depend on > other modules in the same layer. Wonderful! > This means for example that the > client can completely discard Bind if she does not need it; or ^ that should be a comma > perhaps take out Operator and Statement and just use Function, which ^^^^^^^^^^^^ "she can leave" > is desireable in a pure FP application. ^^ "would be" > > The library has grown from the original Phoenix but still comprises > of only header files. There are no object files to link against. ^^ strike > Core > > The lowest two layers comprise the core. > > The Actor is the main concept behind the library. Lazy functions are > abstracted as actors which are actually polymorphic functors. That is one scary sentence. Can you simplify it? What are you really trying to say? > There are only 2 kinds of actors: > > 1. Primitives > 2. Composites > > Composites are composed of zero or more actors. Each actor in a > composite can again be another composite. Primitives are atomic > units and are not decomposable. Again, what does "decomposable" mean? > Modules > > Module Description > > Function Lazy functions support (e.g. add) > > Operator Lazy operators support (e.g. +) > > Statement Lazy statments (e.g. if_, while_) > > Object Lazy casts (e.g. static_cast_), object creation > destruction (e.g. new_, delete_) > Scope Support for scopes, local variables and lambda-lambda "lambda-lambda?" > Bind Lazy functions from simple monomorphic, plain functions, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Can't you say this with 1 or 2 words instead of 4? > member functions or member variables for deferred evaluation. ^^^^^^^^^^^^^^^^ "data members" What does "for deferred evaluation" add here? > Intrinsic Set of predefined "lazy" functions that work on STL ^^^^^^ strike > containers and sequences (e.g. push_back). I would call that module "container." It isn't the intrinsics of the phoenix library, but of the STL container library. > Algorithm Set of predefined "lazy" versions of the STL ^^^^^^ strike. > algorithms (e.g. find_if). > Includes > Module File > Core #include <boost/spirit/phoenix/core.hpp> > Function #include <boost/spirit/phoenix/function.hpp> > Operator #include <boost/spirit/phoenix/operator.hpp> > Statement #include <boost/spirit/phoenix/statement.hpp> > Object #include <boost/spirit/phoenix/object.hpp> > Scope #include <boost/spirit/phoenix/scope.hpp> > Bind #include <boost/spirit/phoenix/bind.hpp> > Intrinsic #include <boost/spirit/phoenix/intrinsic.hpp> > Algorithm #include <boost/spirit/phoenix/algorithm.hpp> At this point in the docs you'd do better to write it in English: Each module is defined in a header with the same base name. So for example, the core module is in <boost/spirit/phoenix/core>. > Finer grained include files are available per feature. See the ^ a semicolon would be good here > succeeding sections. -- Dave Abrahams Boost Consulting www.boost-consulting.com

3 2

Gender neutral documentation (was RE: [ANN] Phoen ix-2 prerelease)
by Martin Bonner 05 Nov '05

05 Nov '05

David Abrahams <dave(a)boost-consulting.com> writes: > Joel de Guzman <joel(a)boost-consulting.com> writes: >> This means for example that the >> client can completely discard Bind if she does not need it; or > ^ > that should be a comma > >> perhaps take out Operator and Statement and just use Function, which > ^^^^^^^^^^^^ > "she can leave" Is there a boost convention on gender neutral language? I approve of the sentiment behind using "she" (there aren't enough women in technical roles), but I do find myself stumbling every time I read it. My personal preference is to use "they" as the first person singular gender-neutral pronoun. This will be /intensely/ irritating to grammar purists, but does seem to be the way the language is evolving. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

7 8

Boost File Vault broken
by Jose 04 Nov '05

04 Nov '05

http://www.boost-consulting.com/vault/ The html in the page is broken (see near search box). Also, the site is incredibly slow (either the website or the PHP pages) Can anybody fix this ?

3 4

Re: [boost] [ANN] Phoenix-2 prerelease (supported operators)
by David Abrahams 04 Nov '05

04 Nov '05

Joel de Guzman <joel(a)boost-consulting.com> writes: > Comments, feedback very welcome! > Supported operators Style tip: every section should have some introductory text before its first subsection. Every subsection should have at least one sibling. > Unary operators > > prefix: ~, !, -, +, ++, --, & (reference), * (dereference) > postfix: ++, -- > > Binary operators > > =, [], +=, -=, *=, /=, %=, &=, |=, ^=, <<=, >>= > +, -, *, /, %, &, |, ^, <<, >> > ==, !=, <, >, <=, >= > &&, ||, ->* > > Ternary operator > > if_else(c, a, b) > > The ternary operator deserves special mention. Since C++ does not > allow us to overload the conditional expression: c ? a : b, the > if_else pseudo function is provided for this purpose. The behavior > is identical, albeit in a lazy manner. Does it deserve special support? Why not just use if_(c)[a].else[b] ? > Member pointer operator > > a->*member_object_pointer > a->*member_function_pointer > > The left hand side of the member pointer operator must be an actor > returning a pointer type. The right hand side of the member pointer > operator may be either a pointer to member object or pointer to > member function. > > > If the right hand side is a member object pointer, the result is a > composite providing lazy access to that member. "an actor that, when invoked, returns a reference to that member." > For example: > > struct A > { > int member; > }; > > A* a = new A; > ... > > (arg1->*&A::member)(a); // returns member a->member > > If the right hand side is a member function pointer, the result is a > delayed function call. The arguments to this call are then bound to > the returned composite. The wording is confusing. "Delayed function call" has not been defined. Why not just say that "the result is an actor that, when invoked, calls the specified member function?" Is that inaccurate? -- Dave Abrahams Boost Consulting www.boost-consulting.com

2 1

Re: [boost] [ANN] Phoenix-2 prerelease (Operators)
by David Abrahams 04 Nov '05

04 Nov '05

Joel de Guzman <joel(a)boost-consulting.com> writes: > Comments, feedback very welcome! > Operator > > Lazy operators... ^^^^^^^^^^^^^^^^^ What is this doing here? What is the ellipsis for? > This facility provides a mechanism for lazily evaluating > operators. Syntactically, a lazy operator looks and feels like an > ordinary C/C++ infix, prefix or postfix operator. The operator > application looks the same. However, unlike ordinary operators, the > actual operator execution is deferred. Samples: > > arg1 + arg2 > 1 + arg1 * arg2 > 1 / -arg1 > arg1 < 150 > > We have seen the lazy operators in action (see Quick Start). Let's > go back and examine it a little bit further: ^^ "them" > > find_if(c.begin(), c.end(), arg1 % 2 == 1) > > Through operator overloading, the expression arg1 % 2 == 1 actually > generates a composite. The fact that it's a composite (as opposed to a primitive) is of no interest at all to the user at this point. I would say "a function object" or "an actor." There's way too much emphasis on this whole composite/primitive distinction. > This composite object is passed on to STL's > find_if function. This is a place where you really see how not using any qualification hurts. Should be std::find_if, to distinguish it from the library's lazy find_if that can be passed to higher-order functions. > In the viewpoint of STL, the composite is simply a ^^ "From" > function object expecting a single argument > , the container's element. ^^^^^^^^^^^^^^^^^^^^^^^ "of the container's value_type." > For each element in the container c, the element is passed ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ "Each element in c" > on as an argument arg1 to the composite (function object). The ^^^^ strike. That is not the name of the argument. > composite checks if this is an odd value based on the expression > arg1 % 2 == 1 where arg1 is iteratively replaced by the container's ^^^^^^^^^^^ ??? > element. > > A set of classes implement all the C++ free operators. ^^^^^^^ Really, the operators are implemented by a set of classes? Seems bizarre. Also seems irrelevant to the reader. > Like lazy functions (see function), lazy operators are not > immediately executed when invoked. Instead, a composite (see > composite) object is created and returned to the caller. Example: > > (arg1 + arg2) * arg3 > > does nothing more than return a composite. A second function call will evaluate the actual operators. Example: > > int i = 4, j = 5, k = 6; > cout << ((arg1 + arg2) * arg3)(i, j, k); > > will print out "54". > > Arbitrarily complex expressions can be lazily evaluated following > three simple rules: That sentence doesn't make sense to me. "Can be" would apply to what the user can do, but the rules describe what the library does. Maybe "...are lazily evaluated according to these three rules:" I'm not sure that "Arbitrarily complex" adds anything. It would make sense in the context of what the user can do: "Arbitrarily complex epressions can be made lazy by following..." but then, that's incompatible with what follows. > 1. Lazy evaluated binary operators apply when at least one of the > operands is an actor object (see actors, primitives and > composite). Consequently, if one of the operands is not an actor > object, it is implicitly converted, by default, to a value (see > values). > 2. Lazy evaluated unary operators apply only to operands which > are actor objects. > 3. The result of a lazy operator is a composite actor object that > can in turn apply to rule 1 and 2. The actor applies to the rules, or the rules apply to the actor? This may seem like nitpicking, but the above can only make sense if you already know what it's saying, because you'll overlook the logical inconsistencies. It won't help the person who's trying to understand the library from the outside. > The one exception is the member pointer operator ->*, as we shall > see later. As long as you're spelling out the rules in detail, you should add the one exception immediately, so the user can read them all in one place. > Example: > > -(arg1 + 3 + 6) > > 1. Following rule 1, lazy evaluation is triggered since arg1 is > an actor (see primitives). You have to say what part of the expression is being evaluated! In this case, arg1 + 3 > 2. The immediate right operand: 3 is implicitly converted to a > value. Still following rule 1. > > 3. The result of this arg1 + 3 expression is a composite object, > following rule 3. > > 4. Now since arg1 + 3 is a composite, following rule 1 again, its > right operand: 6 is implicitly converted to a value. > > 5. Continuing, the result of arg1 + 3 ... + 6 is again another > composite. Rule 3. > > 6. The expression arg1 + 3 + 6 being a composite, is the operand > of the unary operator -. Following rule 2, the result is an actor > object. > 7. Following rule 3, the whole thing -(arg1 + 3 + 6) is a composite. > > Confused? If so, it's because you're exposing way more detail than the user needs, IMO. All this stuff could be better explained by a section titled How to know when the result of an expression is an actor > well, when in doubt, just wrap the operands in ref(x), val(x) or > cref(x) appropriately and you'll be ok: > > -(arg1 + val(3) + val(6)) How does the above help unconfuse the reader? > Lazy-operator application is highly contagious. In most cases, a ^^^^^^^^^^^^^^^^^^^^^^^^^ "Laziness" > single argN actor infects all its immediate neighbors within a group > (first level or parenthesized expression). > > > Take note that although at least one of the operands of what? > must be a valid actor class in order for lazy evaluation to take > effect, if this is not the case and we still want to lazily evaluate > an expression, we can use ref(x), val(x) or cref(x) to transform the > operand into a valid action object (see primitives). Example: ^^^^^^ actor > > val(1) << 3; Note that at least one operand of any operator must be a valid actor for lazy evaluation to take effect. To force lazy evaluation of an ordinary expression, we can use ref(x), val(x) or cref(x) to transform an operand into a valid actor object. For example, val(1) << 3; -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Re: [boost] Gender neutral documentation
by Martin Bonner 04 Nov '05

04 Nov '05

----Original Message---- From: Angus Leeming [mailto:angus.leeming@btopenworld.com] Sent: 04 November 2005 11:13 To: boost(a)lists.boost.org Subject: Re: [boost] Gender neutral documentation > Anthony Williams wrote: >> The use of "she" implies the person in question is female. Though >> "he" technically also has the implication that the person is male, >> it is general usage that "he" is used as a stand in for "he or she". >> If we really want to be gender neutral, we should write "he or she", >> which is what we really mean. Sometimes this is abbreviated "s/he", >> but that's an ugly kludge. Better would be to rewrite the sentence >> to avoid the issue. > >>> My personal preference is to use "they" as the first person >>> singular gender-neutral pronoun. This will be /intensely/ >>> irritating to grammar purists, but does seem to be the way the >>> language is evolving. > >> I don't like this, but it is preferable to "she". > > We do have a pronoun for just such a usage, albeit one that appears to > be used today only by the British royal family. Perhaps it sounds > archaic, but one understands what one is talking about when one uses > the correct language. We do. However what one *meant* to write was: One's personal preference is to use "they" as the *THIRD* person singular gender-neutral pronoun. As used by the British royal family, "one" is a first person singular pronoun. > Regards from yet another Brit, :-) -- 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

Re: [boost] Feature Request
by Victor A. Wagner Jr. 04 Nov '05

04 Nov '05

At 22:40 2005-11-03, Abajyan, Hambardzum wrote: >Hi >(I've already been subscribed my address as you told me to do.) > >I would like to now why there isn't an implementation of TCP(UDP) >Sockets ? >I think it's possible to write a good platform-independent architecture >based on Berkeley socket interface (supporting asynchronous >(non-blocking) sockets), because both Linux and Windows systems support >that architecture. >There are many libraries like that: e.g. Boost.Thread library which is >also platform-independent. In my opinion, this feature is very usefull >as with it programmers can develop network applications on Boost. >Thanks I like the approach these guys are taking: http://www.dtilib.dk/ that actually would be 3 libraries, but I like them all. > >Best Regards Hambik > >_______________________________________________ >Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

3 2

Re: [boost] [ANN] Phoenix-2 prerelease (Functions)
by David Abrahams 04 Nov '05

04 Nov '05

Joel de Guzman <joel(a)boost-consulting.com> writes: > Comments, feedback very welcome! > Function > > Lazy functions... > > #include <boost/spirit/phoenix/function/function.hpp> > > The function template class provides a mechanism for lazily ^^^^^^^^^^^^^^ class template > evaluating functions. Syntactically, a lazy function looks like an > ordinary C/C++ function. The function call looks familiar and feels > the same as ordinary C++ functions. Except you can't use ADL. > However, unlike ordinary > functions, the actual function execution is deferred. For example > here are sample factorial function calls: Whoa, where did factorial come from? > factorial(4) > factorial(arg1) > factorial(arg1 * 6 / factorial(ref(i))) > > These functions are automatically lazily bound Really? Even the first one? > unlike ordinary function pointers or functor objects that need to be > explicitly bound through the bind function (see Bind). > > A lazy function works in conjunction with a user defined function > object (as usual with a member operator()). I'm lost. What do you mean "in conjunction with?" > Only special forms of function objects are allowed. Even more lost! Allowed where? > This is required to enable true polymorphism I happen to have a clue as to what you mean, but most won't. Probably anyplace you mention polymorphism in this doc, you should link to the discussion of its use in this context. > (STL style monomorphic functors and function pointers can still be > used through the bind facility (see Bind)). > > > This special function object is expected to have a nested template > class apply<T0...TN> (where N is the number of arguments of its > operator()). The nested template class result should have a typedef > type that reflects the return type of its operator(). I guess you might be describing the Eval concept. It's not obvious though. This section needs to be reworked for clarity. > There is a special case Of what? > for functors that accept no arguments. Such nullary functors are > only required By what? > to define a typedef result_type that reflects the > return type of its operator(). > > > Here's an example of a simple functor that computes the factorial of > a number: I would avoid "functor" except as a parenthesized note remarking that function objects are often called functors in the C++ community. That usage of "functor" is sorta deprecated and probably never should have arisen, considering its prior use with other meanings. > struct factorial_impl > { > template <typename Arg> > struct apply > { > typedef Arg type; > }; > > template <typename Arg> > Arg operator()(Arg n) const > { > return (n <= 0) ? 1 : n * this->operator()(n-1); > } > }; > > (See factorial.cpp) Oh, here it is. Way too late. Or mentioned too early. > The functor is polymorphic. Its arguments and return type are not > fixed to a particular type. The example above can handle any Arg > type as long as it can carry out the required operations (i.e. <=, * > and - ). > > We can declare and instantiate a lazy factorial function this way: > > function<factorial_impl> factorial; Oh, this is the point of the section? Then why is it called "Function" set in normal type, instead of "function" set in code font? > Invoking a lazy function factorial does not immediately execute the function object factorial_impl. Instead, a composite object is created and returned to the caller. Example: > > factorial(arg1) Even in factorial(4) ? > does nothing more than return a composite. A second function call > will invoke the actual factorial function. Example: > > int i = 4; > cout << factorial(arg1)(i); > > will print out "24". > > Take note that in certain cases (e.g. for function objects with > state), an instance of the functor may be passed on to the > constructor. Example: > > function<factorial_impl> factorial(ftor); > > where ftor is an instance of factorial_impl (this is not necessary ^^^^ needs antecedent > in this case since factorial is a simple stateless functor). Take ^^^^ too many "this"es. Eliminate the first. > care though when using functors with state because the functors are ^^^^^^ ^ strike , > held by value. I don't think you mean that. I think you mean "Functors are often copied repeatedly, and the state may be changed in one or more copies, rather than in the original." > It is best to keep the data manipulated by a functor > outside the functor itself and keep a reference to this data inside > the functor. Also, it is best to keep functors as small as possible. > -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Re: [boost] [ANN] Phoenix-2 prerelease
by David Abrahams 04 Nov '05

04 Nov '05

Joel de Guzman <joel(a)boost-consulting.com> writes: > Comments, feedback very welcome! > Values > > #include <boost/spirit/phoenix/core/value.hpp> > > Whenever we see a constant in a partially applied function, an > > actor<value<T> > > > (where T is the type of the constant) is automatically created by > default for us. > For instance: > > add(arg1, 6) > > Passing a second argument, 6, an actor<value<int> > is implicitly > created behind the scenes. This is also equivalent to: > > add(arg1, val(6)) > > val(x) generates an actor<value<T> > where T is the type of x. I think the use of "us" here is awkward. "You" would be better. "automatically by default" is confusing language. If you're not prepared to tell people what happens when the default is not taken, you probably shouldn't mention that it's a default at all. Also, I doubt that it's really _wherever_ a constant appears in a partially applied function: foo<2>() + arg1 I suggest: To represent a value of type T as an actor, we can use the value template. actor<value<T> >(x) is an actor that returns x when invoked. For instance, actor<value<int> >(6) is equivalent to val(6) an actor that, when invoked, returns the value 6. In expressions combining actors with values, the val() function is invoked implicitly, so add(arg1, 6) is equivalent to add(arg1, val(6)) an actor that adds 6 to its first argument. > In most cases, there's really no need to explicitly use val. There ^^^^^^ strike > are situations though, as we'll see later on, where this is > unavoidable. ..., but as we'll see later on, there are situations where it is unavoidable. -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Boost regression notification (2005-11-04 [RC_1_33_0])
by Douglas Gregor 04 Nov '05

04 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-04T14:47:07Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

1 0

Boost regression notification (2005-11-04 [HEAD])
by Douglas Gregor 04 Nov '05

04 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-04T06:00:10Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 294 failures in 13 libraries: bind (7) concept_check (12) graph (2) io (1) mpl (1) serialization (30) spirit (8) thread (4) tr1 (147) tuple (1) type_traits (58) typeof (18) xpressive (5) |bind| bind_dm3_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_array: gcc-2.95.3-linux std_test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 std_test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_function: gcc-2.95.3-linux std_test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_hash: gcc-2.95.3-linux std_test_mem_fn: gcc-2.95.3-linux std_test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_random: gcc-2.95.3-linux std_test_reference_wrapper: gcc-2.95.3-linux std_test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_functional: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_memory: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tr1_add_const_test: gcc-2.95.3-linux tr1_add_cv_test: gcc-2.95.3-linux tr1_add_pointer_test: gcc-2.95.3-linux tr1_add_reference_test: gcc-2.95.3-linux tr1_add_volatile_test: gcc-2.95.3-linux tr1_aligned_storage_test: gcc-2.95.3-linux tr1_alignment_of_test: gcc-2.95.3-linux tr1_extent_test: gcc-2.95.3-linux tr1_has_nothrow_assign_test: gcc-2.95.3-linux tr1_has_nothrow_constr_test: gcc-2.95.3-linux tr1_has_nothrow_copy_test: gcc-2.95.3-linux tr1_has_trivial_assign_test: gcc-2.95.3-linux tr1_has_trivial_constr_test: gcc-2.95.3-linux tr1_has_trivial_copy_test: gcc-2.95.3-linux tr1_has_trivial_destructor_test: gcc-2.95.3-linux tr1_has_virtual_destructor_test: gcc-2.95.3-linux tr1_is_abstract_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin tr1_is_arithmetic_test: gcc-2.95.3-linux tr1_is_array_test: gcc-2.95.3-linux tr1_is_base_of_test: gcc-2.95.3-linux tr1_is_class_test: gcc-2.95.3-linux tr1_is_compound_test: gcc-2.95.3-linux tr1_is_const_test: gcc-2.95.3-linux tr1_is_convertible_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_empty_test: gcc-2.95.3-linux tr1_is_enum_test: gcc-2.95.3-linux tr1_is_floating_point_test: gcc-2.95.3-linux tr1_is_function_test: gcc-2.95.3-linux tr1_is_fundamental_test: gcc-2.95.3-linux tr1_is_integral_test: gcc-2.95.3-linux tr1_is_member_func_test: gcc-2.95.3-linux tr1_is_member_obj_test: gcc-2.95.3-linux tr1_is_member_pointer_test: gcc-2.95.3-linux tr1_is_object_test: gcc-2.95.3-linux tr1_is_pod_test: gcc-2.95.3-linux tr1_is_pointer_test: gcc-2.95.3-linux tr1_is_polymorphic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_reference_test: gcc-2.95.3-linux tr1_is_same_test: gcc-2.95.3-linux tr1_is_scalar_test: gcc-2.95.3-linux tr1_is_signed_test: gcc-2.95.3-linux tr1_is_union_test: gcc-2.95.3-linux tr1_is_unsigned_test: gcc-2.95.3-linux tr1_is_void_test: gcc-2.95.3-linux tr1_is_volatile_test: gcc-2.95.3-linux tr1_rank_test: gcc-2.95.3-linux tr1_remove_all_extents_test: gcc-2.95.3-linux tr1_remove_const_test: gcc-2.95.3-linux tr1_remove_cv_test: gcc-2.95.3-linux tr1_remove_extent_test: gcc-2.95.3-linux tr1_remove_pointer_test: gcc-2.95.3-linux tr1_remove_reference_test: gcc-2.95.3-linux tr1_remove_volatile_test: gcc-2.95.3-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

Global object initialization [was: Phoenix-2 prerelease]
by David Abrahams 04 Nov '05

04 Nov '05

Joel de Guzman <joel(a)boost-consulting.com> writes: > Comments, feedback very welcome! Here are some sample preset definitions of arg1..argN actor<argument<0> > const arg1 = argument<0>(); actor<argument<1> > const arg2 = argument<1>(); actor<argument<2> > const arg3 = argument<2>(); and its BLL_1.._N style counterparts: You shouldn't use the BLL abbrev., especially not without introducing it first. I suggest "Boost.Lambda" actor<argument<0> > const _1 = argument<0>(); actor<argument<1> > const _2 = argument<1>(); actor<argument<2> > const _3 = argument<2>(); Have you considered the ODR/initialization order implications of this? Eric and I have been discussing this in another context, and it seems to us that you have a choice: 1. The placeholders are statically initialized const POD objects in an unnamed namespace and you have likely ODR violation when used by templates in multiple translation units. 2. The placeholders are dynamically initialized references in an unnamed namespace and you risk undefined behavior when they are used without initialization due to initialization order issues 3. The placeholders are dynamically initialized objects in an unnamed namespace, and you have likely ODR violation *and* initialization order issues Seems from the doc like you have #3, which is the worst of both worlds. No? -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Re: [boost] [ANN] Phoenix-2 prerelease
by David Abrahams 04 Nov '05

04 Nov '05

Joel de Guzman <joel(a)boost-consulting.com> writes: > Comments, feedback very welcome! template <typename Eval> struct actor : Eval { return_type operator()() const; template <typename T0> return_type operator()(T0& _0) const; template <typename T0, typename T1> return_type operator()(T0& _0, T1& _1) const; //... }; Is that really what the declaration of actor looks like? I have a hard time believing that there's an identifier called return_type involved. IMO this is just confusing. Are you sure you want to show any code here at all? Oh! and you're using _0, _1, et. al. as parameter names! Wow, really confusing! -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

[MPL.Math] semantics of integral_part and fractional_part metafunctions
by Cromwell Enage 04 Nov '05

04 Nov '05

--- Manfred Doubar wrote: > BUT I would expect that both integer and fractional > _parts *included* the sign - and I tend to think > anything else would inevitably lead to confusion. I set up the current semantics of is_negative, integral_part, and fractional_part to match the semantics of the corresponding typedefs in mixed_number_impl. BTW, integral_part used to be called whole_part because it returned whole numbers, which were were nonnegative. > I have a good hint of why you might have gone down > this path, Now you know exactly why. > but I can only think that its going to be cause for > error. No, the difference between our definitions of integral_part and fractional_part will be the cause for error. It turns out that Mathematica <http://mathworld.wolfram.com/> agrees with you, so I'll go ahead and change the metafunction semantics. Cromwell D. Enage __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

2 2

Re: [boost] [ANN] Phoenix-2 prerelease
by David Abrahams 04 Nov '05

04 Nov '05

zvrba(a)globalnet.hr writes: > On Thu, Nov 03, 2005 at 04:55:59PM -0500, David Abrahams wrote: >> >> Rewrite that paragraph: >> > Totally off-topic, but while you're at it.. > > 1. Where did you learn these elements of style? Any online > references? http://www.amazon.com/exec/obidos/tg/detail/-/020530902X/103-0796082-472383… > 2. As for asne.org. Can you please give some navigation on the site > where to find editorial tips (how did you find e.g. > http://www.asne.org/index.cfm?ID=4364 ?) Google. > Is there an index of such tips?o I dunno. > I'm asking because I've found out for myself how hard it is to write a > good, clear and concise text... Strunk & White is the bible. -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Website spelling error (still there)
by Jeffrey Williams 04 Nov '05

04 Nov '05

A while back I reported a web site spelling error to this list. It is still there. Which means either I am reporting it to the wrong place, or noone cares or perhaps I am wrong about the spelling error. I'll report it again: On the boost home page, under the latest news in the Serialization library section is says this: Improved seialization of shared pointers Shouldn't this be: Improved serialization of shared pointers Or in the field of serialization does "seialization" actually have a specific meaning? Jeff

1 0

[network] Boost.Network proposal v0.4
by Pedro Lamarão 04 Nov '05

04 Nov '05

Fellow Boosters, this is an update on my proposal for (the beggining of?) a Boost.Network library, located in the "Input - Output" folder of the Sandbox. I consider it feature complete for a 1.0 milestone; the features being: * IOStreams through boost::iostreams (providing a "talker" type model of Device over sockets). * A listener class. * A wrapper for the name resolution services of the system library. * Types to store network addresses with formatted output operators. There's still some more documentation to write, though. Please give one last shot at this proposal. Last time people objected to it as a "Boost.Network" library for not being sufficiently generic (in which it doesn't support "multiplexing" or "asynchronicity"), so perhaps I should move it deeper inside, like, Boost.IOStreams.Network. What do you think? The four components provided could be considered independently: the listener class is as simple as it gets, with a private "accept" method for RAII initialization of whatever socket wrapper type; the model of Device is also as simple as it gets; maybe there is some other interesting stuff to improve the getaddrinfo wrapper and the address types. Possible areas of improvement for the future are: * selector/poller (which is sitting around here waiting) * full formatted input and output for address types * asynchronous resolver (based on Boost.Threads). * Wrapper for sendfile/TransmitFile. -- Pedro Lamarão

2 2

[Boost-bugs] [ boost-Bugs-1348061 ] regex fails to Compile unter Windows and VC++ 7.1
by SourceForge.net 04 Nov '05

04 Nov '05

Bugs item #1348061, was opened at 2005-11-04 01:11 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1348061&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: regex Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: John Maddock (johnmaddock) Summary: regex fails to Compile unter Windows and VC++ 7.1 Initial Comment: Hello regex-Developers I have tried to download boost_1_33_0.zip and install boost regex on Windows 2000 using Microsoft Visual Studio .NET 1.1 (C++ compiler version 7.1). Unfortunately, after changing to boost_1_33_0 \libs\regex\build and running nmake -fvc71.mak I get the error that VC++ doesn't know how to make "allocator.hpp" and "regex_library_include.hpp" It appears that allocator.hpp and regex_library_include.hpp are both missing in version 1.33. I copied the files from the 1.32 version, and that solved my problem. Everything compiles fine and seems to work nicely now. Not sure why these files are missing... Could you please include them into the 1.33- version again (they go into boost_1_33_0 \boost\regex\config). Thanks and best regards /Christoph Hänle. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1348061&group_… ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] vc8 failures in bind mem_fn_eq
by Victor A. Wagner Jr. 04 Nov '05

04 Nov '05

At 04:14 2005-11-03, Bronek Kozicki wrote: >On 11/3/05, Victor A. Wagner Jr. <vawjr(a)rudbek.com> wrote: > > has the problem been fixed? the results from metacomm show that my > > run at 2005/11/02T2200 has no failures in bind. > >I can definitely see failed test in my today's results. any thoughts on why they're not in my results? the last results of yours I see "posted" are: Wed, 2 Nov 2005 19:01:46 +0000 >B. > >-- >Bronek Kozicki brok(a)spamcop.net http://b.kozicki.pl/ > >_______________________________________________ >Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

1 0

Feature Request
by Abajyan, Hambardzum 04 Nov '05

04 Nov '05

Hi (I've already been subscribed my address as you told me to do.) I would like to now why there isn't an implementation of TCP(UDP) Sockets ? I think it's possible to write a good platform-independent architecture based on Berkeley socket interface (supporting asynchronous (non-blocking) sockets), because both Linux and Windows systems support that architecture. There are many libraries like that: e.g. Boost.Thread library which is also platform-independent. In my opinion, this feature is very usefull as with it programmers can develop network applications on Boost. Thanks Best Regards Hambik

1 0

Re: [boost] Sermon at the Soup Kitchen
by Michael D. Crawford 04 Nov '05

04 Nov '05

Peter Dimov saved me from a collosal blunder by correcting my impression that shared_ptr wasn't thread-safe. I've posted a revised draft here: http://www.goingware.com/tips/smart-pointers-and-automated-testing/#thread-… I hadn't previously understood that thread-safety is not an all or nothing proposition, that is, that one can only guarantee that certain kinds of simultaneous operations will work. My revised text points that out and quotes the first paragraph of shared_ptr's doc on thread safety. I *did* know that there are different degrees of exception safety, so I compare thread-safety guarantees to that. When I cover exception safety in a week or so I'll discuss what that means; sometimes for reasons of performance or memory conservation, one must choose not to be completely exception-safe. Sermon at the Soup Kitchen http://www.goingware.com/tips/smart-pointers-and-automated-testing/ It's going to be about three hours before I post the final section and submit to Kuro5hin. My first try at "The Right Tool for the Job" in my Kuro5hin diary was characterized by one K5 member as "Utterly incomprehensible", and I realize now he's absolutely correct, so I need to address that. I'm going to add a small section to it that I think I'll call "Every Engineer's Solemn Duty" that exhorts the reader to do the right thing when his company plows ahead with a disastrous engineering decision, even if one risks losing one's job, getting blacklisted, sued or even imprisoned. I don't think most engineers ever spend much time thinking about such things until they are suddenly faced with actually making the awful decision to issue an ultimatum, as I did, or blow the whistle, as I still might. I'm lucky I only lost my job. Think of the poor Morton Thiokol engineer who didn't trust his conscience when he knew the Space Shuttle's O-rings had frozen. He settled for reporting the risk of explosion through company channels, and trusted that Morton Thiokol would do the right thing. By not raising Hell and going directly to NASA when he realized the launch hadn't been canceled, he allowed seven people to lose their lives, a billion dollar spacecraft to be destroyed, and the US space program to be set back several years. If I can find a good web page about it, I'm also going to mention the Ford Pinto's exploding gas tank. It came out in a lawsuit that Ford's engineers made a calculated decision to let the gas tank go ahead and explode because they didn't think the cost of paying the inevitable lawsuit damages would be as much as the added manufacturing costs of a safer tank. Before quitting it to run "Yoyodyne" full time, "Jack's" last job was managing a team designing a novel, experimental new medical device, the failure of which would doom the patient to certain death within minutes. I might send a link to "Sermon at the Soup Kitchen" to his ex-employer, along with an explanation of just who Jack and Yoyodyne really are. And yes, I'm well aware that if Jack ever reads my sermons he might try to drag me into court. At least I can sleep soundly at night. You should see all the emails I *don't* post online. Yours, -- Michael D. Crawford

4 5

Active objects?
by Jason Hise 03 Nov '05

03 Nov '05

I watched the talk Herb Sutter gave recently regarding concurrency, and I have to say I find the ideas of active objects and future variables to be very exciting. (A link to the talk is provided below, which must be viewed with Internet Explorer). I noticed that Boost already has a futures library in the sandbox under development, which from what I can tell looks well designed. Are there any plans to add the functionality of active objects to boost as well? I would be interested in hearing how you think the problem would be best approached. From what I can tell, it should ideally be possible to use 'active' as a modifier like 'const' or 'volatile' in front of a specific object instance, and have all member function calls automatically add themselves to a queue when called, instead of actually being called. Because this syntax is probably impossible to pull off, I think the next best thing would look something like the following: struct MyClass { int foo ( int arg1, const char * arg2 ); }; void test ( ) { active < MyClass > object; future < int > i = object.request ( MyClass::foo, 42, "blah" ); } 'request' could also be spelled 'enqueue', 'invoke', or 'operator ()', although I'm not sure if the terseness of the latter would be sensible. 'active' would probably use CRTP to derive privately from 'MyClass', enforcing that member functions of MyClass are not called directly. Thoughts? Herb Sutter's video: http://microsoft.sitestream.com/PDC05/TLN/TLN309_files/Default.htm#nopreloa… -Jason

13 29

Re: [boost] [ANN] Phoenix-2 prerelease
by David Abrahams 03 Nov '05

03 Nov '05

Joel de Guzman <joel(a)boost-consulting.com> writes: > Comments, feedback very welcome! > Actors > > The Actor is the main concept behind the library. Actors are ^^^ strike > function objects (functors). An actor can accept 0 to N arguments ^ "sometimes called" > (where N is a predefined maximum). What does that mean? If I define a function object that accepts fewer than N arguments it can't be an Actor? What is N really? Why not give the actual symbolic name here? > You can set PHOENIX_LIMIT, the predefined maximum arity an actor can > take. By default, PHOENIX_LIMIT is set to 10. Ah, there it is. Still, the use of N seems superfluous. > While the Actor is a concept representing a function, there is also > the actor template class which models the concept. The template > class has a sole template parameter, Eval, from which it derives > from. The actor class doesn't have the smarts to actually evaluate > the function, Eval does. Eval is a concept, representing the > function body (i.e. the implementation of the function). Rewrite that paragraph: Phoenix supplies an actor class template whose specializations model the Actor concept. actor has one template parameter, Eval, that supplies the smarts to actually evaluate the resulting function. It's too early to say that Eval must conform to the Eval concept. > template <typename Eval> > struct actor : Eval > { > return_type > operator()() const; > > template <typename T0> > return_type > operator()(T0& _0) const; > > template <typename T0, typename T1> > return_type > operator()(T0& _0, T1& _1) const; > > //... > }; > > The actor class accepts the arguments through a set of function call > operators for 0 to N arities (Don't worry about the details, for > now. For example, note that we skimp over the details regarding > return_type, above). The arguments are then forwarded to the actor's > Eval for evaluation. As long as you're doing this you could solve the forwarding problem for the first N arguments with 2^N overloads for some reasonable N, say, 5. -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Re: [boost] [ANN] Phoenix-2 prerelease
by David Abrahams 03 Nov '05

03 Nov '05

Joel de Guzman <joel(a)boost-consulting.com> writes: > Comments, feedback very welcome! Basics Almost everything is a function in the Phoenix library that can be evaluated as f(a..n), where n is the function's arity, or number of ^^^^ This notation is not familiar to me. I would have expected: f(a[sub 0], a[sub 1], ...a[sub [italic n]]) (using a made up quickbooky syntax) arguments that the function expects. Operators are also functions. For example, a + b is just a function with arity == 2 (or binary). a + b is the same as add(a, b), a + b + c is the same as add(add(a, b), c). I don't know if remarks like Amusingly, functions may even return functions. We shall see what this means in a short while. assume a background that's compatible with your use of the lambda symbol on that page with no explanation. The expression arg1 % 2 == 1 evaluates to a lambda function. arg1 represents an unsupplied argument. I would say arg1 is a placeholder for an argument to be supplied later or if you need a short term for such a thing, arg1 is lazy argument---a placeholder for an argument to be supplied later However, in this document and in the examples and tests provided, don't be surprised to see the first and second steps juxtaposed. ^ in order to illustrate the complete semantics of Phoenix expressions -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Re: [boost] [ANN] Phoenix-2 prerelease
by David Abrahams 03 Nov '05

03 Nov '05

Joel de Guzman <joel(a)boost-consulting.com> writes: > Hi, > > Here's a pre-release package of Phoenix-2. Jaakko and I agreed > that it will be the basis of the Phoenix and Boost Lambda > merger. This version is Phoenix 1 + Lambda + a lot more. > > Take note though that this is not a drop-in replacement of > Phoenix-1 for Spirit users. In particular, there is no > closure support. Phoenix-2 has true local variables. The > plan for Spirit-2 is to replace closures with local variables. > > Docs: http://tinyurl.com/77pz5 > > The pre-release package is here: > http://spirit.sourceforge.net/dl_more/phoenix_v2.zip > > Just drop it where Phoenix-1 is and run the examples/tests. > Comments, feedback very welcome! Composites What we have seen so far, are what are called primitives. You can think of primitives (such as values, references and arguments) as atoms. They are not decomposable. ^^^^^^^^^^^^^^^^^^^^^^^^^ What does that mean to me, the reader? Is not this primitive/composite distinction purely an implementation detail? -- Dave Abrahams Boost Consulting www.boost-consulting.com

2 1

Re: [boost] [ANN] Phoenix-2 prerelease
by David Abrahams 03 Nov '05

03 Nov '05

Joel de Guzman <joel(a)boost-consulting.com> writes: > Comments, feedback very welcome! Lazy Functions As you write more lambda functions, you'll notice certain patterns that you wish to refactor as reusable functions. When you reach that point, you'll wish that ordinary functions can co-exist with phoenix functions. Unfortunately, the immediate nature of plain C++ functions make them incompatible. Lazy functions are your friends. The library provides a facility to make lazy functions. The code below is a rewrite of the is_odd function using the facility: struct is_odd_impl { template <typename Arg> struct apply { typedef bool type; }; template <typename Arg> bool operator()(Arg arg1) const { return arg1 % 2 == 1; } }; I kept looking for where the library facility was in use... and then I saw this: function<is_odd_impl> is_odd; ^^^^^^^^ I guess that's it. It would help to leave a phoenix:: qualification on names from the library, or if you can't do that, use color or bold to emphasize them. Y'know, what I really expected, though, was something I could pass the old is_odd function to: make_function(is_odd) -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Boost regression notification (2005-11-03 [RC_1_33_0])
by Douglas Gregor 03 Nov '05

03 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-03T14:11:11Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

1 0

Boost regression notification (2005-11-03 [HEAD])
by Douglas Gregor 03 Nov '05

03 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-03T06:00:37Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 298 failures in 13 libraries: bind (7) concept_check (12) graph (2) io (1) mpl (1) serialization (34) spirit (8) thread (4) tr1 (147) tuple (1) type_traits (58) typeof (18) xpressive (5) |bind| bind_dm3_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_polymorphic_binary_archive_dll: vc-7_1 test_shared_ptr_132_binary_archive_dll: vc-7_1 test_shared_ptr_132_text_warchive: vc-7_1 test_shared_ptr_132_text_warchive_dll: vc-7_1 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_array: gcc-2.95.3-linux std_test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 std_test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_function: gcc-2.95.3-linux std_test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_hash: gcc-2.95.3-linux std_test_mem_fn: gcc-2.95.3-linux std_test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_random: gcc-2.95.3-linux std_test_reference_wrapper: gcc-2.95.3-linux std_test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_functional: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_memory: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tr1_add_const_test: gcc-2.95.3-linux tr1_add_cv_test: gcc-2.95.3-linux tr1_add_pointer_test: gcc-2.95.3-linux tr1_add_reference_test: gcc-2.95.3-linux tr1_add_volatile_test: gcc-2.95.3-linux tr1_aligned_storage_test: gcc-2.95.3-linux tr1_alignment_of_test: gcc-2.95.3-linux tr1_extent_test: gcc-2.95.3-linux tr1_has_nothrow_assign_test: gcc-2.95.3-linux tr1_has_nothrow_constr_test: gcc-2.95.3-linux tr1_has_nothrow_copy_test: gcc-2.95.3-linux tr1_has_trivial_assign_test: gcc-2.95.3-linux tr1_has_trivial_constr_test: gcc-2.95.3-linux tr1_has_trivial_copy_test: gcc-2.95.3-linux tr1_has_trivial_destructor_test: gcc-2.95.3-linux tr1_has_virtual_destructor_test: gcc-2.95.3-linux tr1_is_abstract_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin tr1_is_arithmetic_test: gcc-2.95.3-linux tr1_is_array_test: gcc-2.95.3-linux tr1_is_base_of_test: gcc-2.95.3-linux tr1_is_class_test: gcc-2.95.3-linux tr1_is_compound_test: gcc-2.95.3-linux tr1_is_const_test: gcc-2.95.3-linux tr1_is_convertible_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_empty_test: gcc-2.95.3-linux tr1_is_enum_test: gcc-2.95.3-linux tr1_is_floating_point_test: gcc-2.95.3-linux tr1_is_function_test: gcc-2.95.3-linux tr1_is_fundamental_test: gcc-2.95.3-linux tr1_is_integral_test: gcc-2.95.3-linux tr1_is_member_func_test: gcc-2.95.3-linux tr1_is_member_obj_test: gcc-2.95.3-linux tr1_is_member_pointer_test: gcc-2.95.3-linux tr1_is_object_test: gcc-2.95.3-linux tr1_is_pod_test: gcc-2.95.3-linux tr1_is_pointer_test: gcc-2.95.3-linux tr1_is_polymorphic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_reference_test: gcc-2.95.3-linux tr1_is_same_test: gcc-2.95.3-linux tr1_is_scalar_test: gcc-2.95.3-linux tr1_is_signed_test: gcc-2.95.3-linux tr1_is_union_test: gcc-2.95.3-linux tr1_is_unsigned_test: gcc-2.95.3-linux tr1_is_void_test: gcc-2.95.3-linux tr1_is_volatile_test: gcc-2.95.3-linux tr1_rank_test: gcc-2.95.3-linux tr1_remove_all_extents_test: gcc-2.95.3-linux tr1_remove_const_test: gcc-2.95.3-linux tr1_remove_cv_test: gcc-2.95.3-linux tr1_remove_extent_test: gcc-2.95.3-linux tr1_remove_pointer_test: gcc-2.95.3-linux tr1_remove_reference_test: gcc-2.95.3-linux tr1_remove_volatile_test: gcc-2.95.3-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

Bug list status
by Marshall Clow 03 Nov '05

03 Nov '05

Four weeks ago: 144 open bugs Three weeks ago: 117 open bugs Two weeks ago: 96 open bugs Last week: 94 open bugs Today: 93 open bugs Thanks to everyone who dealt with the bugs! [ But we're slowing down - I blame the 1.33.1 release process ;-) ] Here are the currently opened bugs, sorted by assignee. If you think that a bug has been assigned incorrectly, please let me know. P.S. I need someone to fix the bugs in the tokenizer library!! Assignee: agurtovoy <http://sourceforge.net/users/agurtovoy/> Summary: mpl::select2nd on vc6 Bug #: 812263 <http://sourceforge.net/tracker/index.php?func=detail&aid=812263&group_id=75…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: wrong usage of ios_base::narrow Bug #: 989487 <http://sourceforge.net/tracker/index.php?func=detail&aid=989487&group_id=75…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: date_time type conversion warning Bug #: 1069225 <http://sourceforge.net/tracker/index.php?func=detail&aid=1069225&group_id=7…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: local_adjustor::utc_to_local throws 'Time label invalid' Bug #: 1220011 <http://sourceforge.net/tracker/index.php?func=detail&aid=1220011&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: filesytem::directory_iterator portability Bug #: 735403 <http://sourceforge.net/tracker/index.php?func=detail&aid=735403&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem fails in posix with files containing ':' Bug #: 776146 <http://sourceforge.net/tracker/index.php?func=detail&aid=776146&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: clock is not portable Bug #: 788762 <http://sourceforge.net/tracker/index.php?func=detail&aid=788762&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: Boost::Filesystem fails when last character in path is ':' Bug #: 875970 <http://sourceforge.net/tracker/index.php?func=detail&aid=875970&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: filesystem::directory_iterator returns incorrect listing Bug #: 937606 <http://sourceforge.net/tracker/index.php?func=detail&aid=937606&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: xtime_cmp: use comparison not subtraction Bug #: 993272 <http://sourceforge.net/tracker/index.php?func=detail&aid=993272&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::exists is broken on cygwin Bug #: 1010681 <http://sourceforge.net/tracker/index.php?func=detail&aid=1010681&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem is systematically broken Bug #: 1012135 <http://sourceforge.net/tracker/index.php?func=detail&aid=1012135&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::native() should reject '/' on non-Win32 Bug #: 1151823 <http://sourceforge.net/tracker/index.php?func=detail&aid=1151823&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::exists has bugs with UNC paths Bug #: 1164057 <http://sourceforge.net/tracker/index.php?func=detail&aid=1164057&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::equivalent does not work on w98 Bug #: 1235262 <http://sourceforge.net/tracker/index.php?func=detail&aid=1235262&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: path and directory_iterator doesn't handle windows root path Bug #: 1259176 <http://sourceforge.net/tracker/index.php?func=detail&aid=1259176&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: no conversion from type to const_type Bug #: 547743 <http://sourceforge.net/tracker/index.php?func=detail&aid=547743&group_id=75…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: EdgeListS = setS for adjacency_list does not work Bug #: 1163077 <http://sourceforge.net/tracker/index.php?func=detail&aid=1163077&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: adjacency_matrix should model BidirectionalGraph Bug #: 1168411 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168411&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA graph adaptors for undirected graphs Bug #: 1168420 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168420&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA adaptors for node_array, edge_array Bug #: 1168424 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168424&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA graph adaptors do not handle hidden nodes properly Bug #: 1168431 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168431&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Generate patches for Graph bugs in 1.32.0 Bug #: 1169920 <http://sourceforge.net/tracker/index.php?func=detail&aid=1169920&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Investigate other kinds of heaps for dijkstra_shortest_paths Bug #: 1170106 <http://sourceforge.net/tracker/index.php?func=detail&aid=1170106&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: function.hpp breaks assign.hpp Bug #: 1181272 <http://sourceforge.net/tracker/index.php?func=detail&aid=1181272&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: vertex bundle properties do not work with VC++.NET 2003 Bug #: 1190394 <http://sourceforge.net/tracker/index.php?func=detail&aid=1190394&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: BGL graph types do not support allocators Bug #: 1193883 <http://sourceforge.net/tracker/index.php?func=detail&aid=1193883&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: random_vertex/random_edge are unnecessarily inefficient Bug #: 1204684 <http://sourceforge.net/tracker/index.php?func=detail&aid=1204684&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Document copy_component Bug #: 1204688 <http://sourceforge.net/tracker/index.php?func=detail&aid=1204688&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: reverse_graph and constness of property maps Bug #: 1246336 <http://sourceforge.net/tracker/index.php?func=detail&aid=1246336&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: html docs frequently missing key words Bug #: 1294420 <http://sourceforge.net/tracker/index.php?func=detail&aid=1294420&group_id=7…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: Miss ' = ParserT()' Bug #: 907299 <http://sourceforge.net/tracker/index.php?func=detail&aid=907299&group_id=75…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: spirit insert_key_actor.hpp Bug #: 1059936 <http://sourceforge.net/tracker/index.php?func=detail&aid=1059936&group_id=7…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: Another config correction for Sun C++ Bug #: 1220782 <http://sourceforge.net/tracker/index.php?func=detail&aid=1220782&group_id=7…> Assignee: dlwalker <http://sourceforge.net/users/dlwalker/> Summary: template problems with common_factor.hpp Bug #: 491637 <http://sourceforge.net/tracker/index.php?func=detail&aid=491637&group_id=75…> Assignee: ebf <http://sourceforge.net/users/ebf/> Summary: boost::blank - missing operators Bug #: 1191356 <http://sourceforge.net/tracker/index.php?func=detail&aid=1191356&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: timeconv.inl to_duration() nsec error Bug #: 548104 <http://sourceforge.net/tracker/index.php?func=detail&aid=548104&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Solaris - once.cpp compile error Bug #: 549162 <http://sourceforge.net/tracker/index.php?func=detail&aid=549162&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: pthread_delay_np() parm incorrect Bug #: 551157 <http://sourceforge.net/tracker/index.php?func=detail&aid=551157&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Bosot.Thread.condition(win32).notify_all Bug #: 551308 <http://sourceforge.net/tracker/index.php?func=detail&aid=551308&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: AIX 4.3 SIGSEGV at thread termination Bug #: 551577 <http://sourceforge.net/tracker/index.php?func=detail&aid=551577&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: boost::threads uses msvc only function? Bug #: 568951 <http://sourceforge.net/tracker/index.php?func=detail&aid=568951&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: threads unnecessary #include Bug #: 571615 <http://sourceforge.net/tracker/index.php?func=detail&aid=571615&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: BCB6 throw EExternelException Bug #: 596149 <http://sourceforge.net/tracker/index.php?func=detail&aid=596149&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: thread_cleanup problems Bug #: 649291 <http://sourceforge.net/tracker/index.php?func=detail&aid=649291&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Mac implementation of threads is CPU hog Bug #: 885045 <http://sourceforge.net/tracker/index.php?func=detail&aid=885045&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: condition variables and recursive_mutex Bug #: 1072605 <http://sourceforge.net/tracker/index.php?func=detail&aid=1072605&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: compiler error on Mac implementation of threads Bug #: 1201779 <http://sourceforge.net/tracker/index.php?func=detail&aid=1201779&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: timeconv.inl line 116 copy/paste error Bug #: 1239052 <http://sourceforge.net/tracker/index.php?func=detail&aid=1239052&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Exception safety in class 'thread' Bug #: 1305885 <http://sourceforge.net/tracker/index.php?func=detail&aid=1305885&group_id=7…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: 'failed fileclone' when building with -j on 1.32.0 Bug #: 1102389 <http://sourceforge.net/tracker/index.php?func=detail&aid=1102389&group_id=7…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: boost jam problem with parallel builds Bug #: 1234224 <http://sourceforge.net/tracker/index.php?func=detail&aid=1234224&group_id=7…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer fails with wchar_t Bug #: 446155 <http://sourceforge.net/tracker/index.php?func=detail&aid=446155&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer not works with Dinkumware 308 Bug #: 458236 <http://sourceforge.net/tracker/index.php?func=detail&aid=458236&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: boost::tokenizer implicit typename Bug #: 912368 <http://sourceforge.net/tracker/index.php?func=detail&aid=912368&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: Tokenizer.hpp doesn't work with BOOST_ENABLE_ASSERT_HANDLER Bug #: 972406 <http://sourceforge.net/tracker/index.php?func=detail&aid=972406&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: Compiler error for tokenizer on Solaris Bug #: 976241 <http://sourceforge.net/tracker/index.php?func=detail&aid=976241&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer and signed char Bug #: 1003889 <http://sourceforge.net/tracker/index.php?func=detail&aid=1003889&group_id=7…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: token_iterator::at_end() result is inversed Bug #: 1338326 <http://sourceforge.net/tracker/index.php?func=detail&aid=1338326&group_id=7…> Assignee: jmaurer <http://sourceforge.net/users/jmaurer/> Summary: Diff in state of mersenne_twister gen between GCC3.41 & CW9 Bug #: 1115124 <http://sourceforge.net/tracker/index.php?func=detail&aid=1115124&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: bug in ublas/storage.hpp Bug #: 1095697 <http://sourceforge.net/tracker/index.php?func=detail&aid=1095697&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: dead links in uBLAS page Bug #: 1169273 <http://sourceforge.net/tracker/index.php?func=detail&aid=1169273&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: Documentation not available on web site: Bug #: 1228242 <http://sourceforge.net/tracker/index.php?func=detail&aid=1228242&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: uBLAS::subslice doesn't work Bug #: 1292635 <http://sourceforge.net/tracker/index.php?func=detail&aid=1292635&group_id=7…> Assignee: johnmaddock <http://sourceforge.net/users/johnmaddock/> Summary: Adding boost::is_complex to type_traits.hpp Bug #: 1315712 <http://sourceforge.net/tracker/index.php?func=detail&aid=1315712&group_id=7…> Assignee: jsiek <http://sourceforge.net/users/jsiek/> Summary: invalid result for File Dependency Examp Bug #: 551110 <http://sourceforge.net/tracker/index.php?func=detail&aid=551110&group_id=75…> Assignee: jsiek <http://sourceforge.net/users/jsiek/> Summary: Spelling of Edmonds-Karp-Algorithm Bug #: 1226292 <http://sourceforge.net/tracker/index.php?func=detail&aid=1226292&group_id=7…> Assignee: mark_rodgers <http://sourceforge.net/users/mark_rodgers/> Summary: Cannot compile octonion_test.cpp because of bug in sinc.hpp Bug #: 751269 <http://sourceforge.net/tracker/index.php?func=detail&aid=751269&group_id=75…> Assignee: mark_rodgers <http://sourceforge.net/users/mark_rodgers/> Summary: Cannot compile octonion_test.cpp because of bug in sinc.hpp Bug #: 751289 <http://sourceforge.net/tracker/index.php?func=detail&aid=751289&group_id=75…> Assignee: nesotto <http://sourceforge.net/users/nesotto/> Summary: boost.range and 'const char[]'. Bug #: 1272315 <http://sourceforge.net/tracker/index.php?func=detail&aid=1272315&group_id=7…> Assignee: nobody Summary: failure in boost jam unit tests on cygwin Bug #: 940941 <http://sourceforge.net/tracker/index.php?func=detail&aid=940941&group_id=75…> Assignee: nobody Summary: Can't build on cygwin Bug #: 1145183 <http://sourceforge.net/tracker/index.php?func=detail&aid=1145183&group_id=7…> Assignee: nobody Summary: crach build bjam from mingw 3.4.4 Bug #: 1341560 <http://sourceforge.net/tracker/index.php?func=detail&aid=1341560&group_id=7…> Assignee: nobody Summary: crach build bjam from mingw 3.4.4 with python Bug #: 1341568 <http://sourceforge.net/tracker/index.php?func=detail&aid=1341568&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: many 'virtual functions vs. non-virtual destructor' warnings Bug #: 1312222 <http://sourceforge.net/tracker/index.php?func=detail&aid=1312222&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: Compiler warning with gcc on Linux Bug #: 1337412 <http://sourceforge.net/tracker/index.php?func=detail&aid=1337412&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: warning caused by size_t to unsigned int conversion on vc++8 Bug #: 1338178 <http://sourceforge.net/tracker/index.php?func=detail&aid=1338178&group_id=7…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: typo in Boost.Test document Bug #: 629685 <http://sourceforge.net/tracker/index.php?func=detail&aid=629685&group_id=75…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: Don't work multilevel hierarchy of test suites in dll. Bug #: 1076691 <http://sourceforge.net/tracker/index.php?func=detail&aid=1076691&group_id=7…> Assignee: samuel_k <http://sourceforge.net/users/samuel_k/> Summary: format: assert when parsing invalid pattern Bug #: 1326132 <http://sourceforge.net/tracker/index.php?func=detail&aid=1326132&group_id=7…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: ct_gcd_lcm.hpp compilation error Bug #: 558174 <http://sourceforge.net/tracker/index.php?func=detail&aid=558174&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: test_pool_alloc.cpp not compile CW8.1 Bug #: 586779 <http://sourceforge.net/tracker/index.php?func=detail&aid=586779&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: pool::purge_memory() does not reset next_size Bug #: 984124 <http://sourceforge.net/tracker/index.php?func=detail&aid=984124&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: Borland compiler error with Pool, boost::pool_allocator Bug #: 988124 <http://sourceforge.net/tracker/index.php?func=detail&aid=988124&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: perfomance: memory cleanup for pool takes too long Bug #: 995270 <http://sourceforge.net/tracker/index.php?func=detail&aid=995270&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: boost::pool_allocator breaks with vector of vectors Bug #: 1179641 <http://sourceforge.net/tracker/index.php?func=detail&aid=1179641&group_id=7…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: Self division wrong in template rational Bug #: 504411 <http://sourceforge.net/tracker/index.php?func=detail&aid=504411&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: Rational sum not optimal for overflows Bug #: 519635 <http://sourceforge.net/tracker/index.php?func=detail&aid=519635&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: rational operator&lt; can overflow Bug #: 798357 <http://sourceforge.net/tracker/index.php?func=detail&aid=798357&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: boost::rational documentation typos(?) Bug #: 1043616 <http://sourceforge.net/tracker/index.php?func=detail&aid=1043616&group_id=7…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: no Boolean conversion for boost::rational Bug #: 1239906 <http://sourceforge.net/tracker/index.php?func=detail&aid=1239906&group_id=7…> Assignee: vladimir_prus <http://sourceforge.net/users/vladimir_prus/> Summary: call to split_winmain raises exception for 8-bit locale Bug #: 1206663 <http://sourceforge.net/tracker/index.php?func=detail&aid=1206663&group_id=7…> Assignee: vladimir_prus <http://sourceforge.net/users/vladimir_prus/> Summary: multitoken broken in program_options 1.33 Bug #: 1266877 <http://sourceforge.net/tracker/index.php?func=detail&aid=1266877&group_id=7…> -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

1 0

Pointer issue
by Luke Anderson 03 Nov '05

03 Nov '05

When I load a serialized pointer (using boost serialization library), there are times when I lose the ability to do certain things to those pointers...for example I cannot delete them at times, cannot add them to vectors, and some other things...What might be causing this behavior __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

2 1

what about making vc8 support official?
by Bronek Kozicki 03 Nov '05

03 Nov '05

I hope that if we deal with python problems, support for vc-8_0 toolset might be officialy endorsed. There will be documentation needed about these PITA warnings and "#pragma warning ..." workaround that Jeff proposed. User would be supposed to put these pragmas before and after including boost headers, but those who care do it anyway because those (and other warnings) are actually triggered by standard library headers shipped with vc8. Doug, what do you think? B.

4 8

Re: [boost] [filesystem] create_symlink() support for Windows Vista?
by Greer, Joe 03 Nov '05

03 Nov '05

> I've mentioned this many times in the past and have been "assured" > that they really aren't "symlinks". > Since I've used *nix about a total of 3 hours in my 4 decade career, > I had to take people at their word. > No, they just act like it in many respects. They are really called reparse points and it is how NTFS supports both symbolic links and mounted volumes. Basically, if the OS sees a reparse point flag set on a directory, it looks up a substitute path in an internal table, substitutes that path and continues parsing the path. This is quite different from symbolic links in *nix, however, they have a similar effect. They also have hard links (much like *nix) which are limited to links within a volume. The Windows resource kit has had tools for this stuff since Windows 2000. joe

1 0

vc8 failures in bind mem_fn_eq
by Bronek Kozicki 03 Nov '05

03 Nov '05

Long list of failures at http://tinyurl.com/8pbw5 It looks as if non-equlity operator fails for all member functions Compiler used is release (not RC nor beta; it's RTM recently published in MSDN downloads) version. Error won't go away with new compiler build, as there won't be any in forseeable future. Peter, do you need help tracing this error? B.

5 12

errors in 1.33.1RC, vc8, boost_signals.dll\vc-8_0\release\threading-multi\named_slot_map.obj...
by Bronek Kozicki 03 Nov '05

03 Nov '05

Error details in attached files. Oddly enough, these errors do not show up in regression tests, but they do appear when building boost manually in release and debug: bjam.exe "-sTOOLS=vc-8_0" -d2 "-sBUILD=release <runtime-link>dynamic <threading>multi <debug-symbols>off" bjam.exe "-sTOOLS=vc-8_0" -d2 "-sBUILD=debug <runtime-link>dynamic <threading>multi <debug-symbols>off" B.

3 2

Re: [boost] Sermon at the Soup Kitchen
by Michael D. Crawford 03 Nov '05

03 Nov '05

I'm going to wait until Morning (Nova Scotia time) before I submit my article to Kuro5hin, as I don't like to sleep while my stories are in moderation. I added a fourth section to my article, which will be the last in this installment. It needs a lot of work. I need to add a few paragraphs yet, but Kuro5hin articles have a hard limit of 64kb because that's how big the database field used to store them can be. I have no doubt I can cut it down while improving my writing, but it's going to take some time. The new section is "The Right Tool for the Job", where I answer brother th0m's question, in response to "auto_ptr and it's Alternatives": "what does the very existence of this topic tell you about C++ as programming language?" http://localhost/goingware/tips/smart-pointers-and-automated-testing/#best-… It took me quite a while to realize I needed to address this in my article, but I discuss a must deeper question every engineer may have to answer for themselves someday. I ask you all to read this, and decide NOW, ahead of time, what you would do if you had to blow the whistle on a bad engineering decision, one that could cause someone's bankrupcy, or put the public at risk: Every Engineer's Solemn Duty http://localhost/goingware/tips/smart-pointers-and-automated-testing/#duty I'm pretty sure there are some other corrections that have been posted that I haven't implemented yet, but I'll make sure I make the revisions soon. The contents of the fourth sermon: IV. The Right Tool for the Job * Brother Mike is Overcome with Grief * Every Engineer's Solemn Duty * Why We Fight * The Most Dangerous Weapon Known to Man Sermon at the Soup Kitchen On C++ Software Quality and Institutional Resistance to Change http://localhost/goingware/tips/smart-pointers-and-automated-testing/ Thanks! -- Michael D. Crawford GoingWare Inc. - Expert Software Development and Consulting http://www.goingware.com/ crawford(a)goingware.com Tilting at Windmills for a Better Tomorrow.

2 1

[filesystem] create_symlink() support for Windows Vista?
by Beman Dawes 03 Nov '05

03 Nov '05

Microsoft has published an API for Windows Vista supporting POSIX-like symbolic links. Unless someone has a killer argument against, I'll add a create_symlink() function to Boost.Filesystem. If anyone volunteers to test it, please let me know. --Beman

5 6

Re: [boost] [1.33.1 Beta] Release is imminent
by BRIDGES Dick 03 Nov '05

03 Nov '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of Jeff Garland > Sent: Tuesday, November 01, 2005 7:27 PM > To: boost(a)lists.boost.org > Subject: Re: [boost] [1.33.1 Beta] Release is imminent > > > On Tue, 1 Nov 2005 14:10:12 -0800, BRIDGES Dick wrote > > Maybe we should wait until Thursday or Friday if we can. > > > > Regards, > > Dick > > For what reason? > > Jeff I am *very* sorry. This missive was supposed to have been forwarded to a co-worker - not sent to the list. I didn't even realize what I had done until reading your reply. A very unpleasant surprise. Sincerest apologies, Dick Bridges

2 1

Sermon at the Soup Kitchen
by Michael D. Crawford 02 Nov '05

02 Nov '05

Friends, I'd like your expert opinions on a C++ article I'm writing. I plan to submit it in a few hours to the community website Kuro5hin (http://www.kuro5hin.org/) I will leave it in "edit mode" until tomorrow, so I'll still have time to revise it to reflect your comments. From my introduction: "When I talk to those guys about how to write better code I have the sense that their experience of me is like going to church." "Many people go to church. How many are without sin?" "But I didn't learn to preach because I studied at the seminary. It is because I was a derelict on skid row until I was saved by..." "... smart pointers and automated testing." Sermon at the Soup Kitchen On C++ Software Quality and Institutional Resistance to Change http://www.goingware.com/tips/smart-pointers-and-automated-testing/ My questions: 0. Am I correct in what I say about the various Boost smart pointers? I say shared_ptr isn't thread safe. Am I right? If so, does Boost::Thread offer a way to make thread-safe reference counted smart pointers? If so, please point out any documentation to me so I can link to it from my piece. 1. I was hired specifically to revamp the company's software development methodology so they achieve high reliability, as even a single incident of failure of their Computer Aided Design product could cost end-users as much as a million dollars if the products designed by it failed to work as designed when manufactured. But when the chips were down, "Yoyodyne" founder "Jack" ordered everyone, me included, to cut corners so we could implement features faster. This led to my ultimatum quoted in the article. I'm now looking for a new job. My question for you is, given that Jack was not a programmer, and didn't have the first clue about how to achieve software quality (nor did the rest of the staff), how could I have overcome the company's resistance to change in such a way that it wouldn't have come to an ultimatum? 2. I have a few links to smart pointer and automated testing pages early in the article, but not many. Can you suggest others? I'm especially interested to hear about other test frameworks, not just for C++ but for *any* language, so that people who don't use C++ still have something to gain by reading my piece. How about frameworks for other kinds of testing than unit testing, like acceptance or integration testing? 3. Can you pick any nits with my assertions about C++ or the various smart pointers? Do you agree with me that the following is a case where auto_ptr is the best choice? Can you think of others? http://www.goingware.com/tips/smart-pointers-and-automated-testing/#when-to… 4. I say early on that neither auto_ptr nor the Boost smart pointers provide all the different kinds of smart pointers one would want. What other kinds can you think of? How would they be implemented? I already have a couple completely implemented, and keep thinking of more, but I'd like ideas for others to discuss in my next installment. I won't tell you my answers yet because I want to stimulate discussion. I'll be placing all my smart pointers under the Boost license and posting a tarball on my website. You're welcome to include them in Boost, but if you don't want to, I'll host them at Sourceforge. 5. I've already been over my article several times looking for grammar and spelling errors, but if you can still find any, please let me know. 6. If you were a sinner before you came to my soup kitchen's service, have I saved your soul? If not, how could I have made my case more effectively? Was your free, hot supper satisfying? Would you come back for more? My article is going to appear in two or three installments at Kuro5hin. The next one, yet to be written, will cover automated testing. I'm also going to cover exception safety, which I feel I have finally come to understand. Depending on how long the second installment is, exception safety might appear there, or in a third installment. I'll discuss the connection between RAII, smart pointers and exception safety. As I deliver each sermon, I'll add it at the link above. Look for them in the table of contents, quoted below. Part I * How I Was Saved o Smart Pointers o Automated Testing * Ultimatum * auto_ptr and Its Alternatives o auto_ptr Doesn't Work for Arrays o Take My Memory. Please! o The Simple Solution o Standard Template Library-Compatible Smart Pointers o That's Great! Is It Thread-Safe Too? o But Arrays? What About the Arrays? o So is auto_ptr Completely Useless? o Without Further Ado * The Right Tool for the Job Part II * The Path of Righteousness Part III * The Holy Grail Thanks for your help! -- Michael D. Crawford GoingWare Inc. - Expert Software Development and Consulting http://www.goingware.com/ crawford(a)goingware.com Tilting at Windmills for a Better Tomorrow.

3 2

Boost regression notification (2005-11-01 [RC_1_33_0])
by Douglas Gregor 02 Nov '05

02 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-01T14:47:09Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

5 6

[Boost-bugs] [ boost-Support Requests-1346197 ] Strange issue with deleting loaded pointers
by SourceForge.net 02 Nov '05

02 Nov '05

Support Requests item #1346197, was opened at 2005-11-02 18:03 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=1346197&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: Luke (jla2w) Assigned to: Nobody/Anonymous (nobody) Summary: Strange issue with deleting loaded pointers Initial Comment: Robert, Thanks for the help on the last issue (object tracking)...One more question. When I save to disk and then load, there are certain things I can no longer do to some of my pointers...i.e. deleting gives me an error, whereas before I could delete the pointers. What might be causing this? Is there a setting that governs the level of access I have to pointers loaded through the serialization library? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1346197&group_… ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[also 1.33.1] VC8 deprecated library functions and impact on boost
by Stefan Slapeta 02 Nov '05

02 Nov '05

Hi all, As some of you know, there is currently a discussion on the C++ lib reflector about the fact that MS decided to "deprecate" some C/C++ standard library functions on their own behalf. Regardless of whether this may be considered good or not: there is definitely an impact on the boost library because this "feature" causes a LOT of warnings in the boost code. FYI, the log of the stage build printed by the VC 8 final release can be read here: http://tinyurl.com/bhxd8 (just search for "deprecated"). Now, as VC 8 has been released at the MSDN site, there will be more and more users dealing with this compiler who will probably be very much confused about the standard conformity of the boost library. Thus, I suggest to generally set the _SCL_SECURE_NO_DEPRECATE macro (which whould suppress those warnings) for this compiler in boost *even for the 1.33.1 release*!! There may be better solutions for future releases, but I think there must be done something now to avoid a lot of user questions! Thoughts? Stefan P.S.: This warning is printed upon EVERY call of cl.exe: cl : Command line warning D9035 : option 'Og' has been deprecated and will be removed in a future release

14 25

Boost regression notification (2005-11-02 [RC_1_33_0])
by Douglas Gregor 02 Nov '05

02 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-02T14:38:13Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

1 0

Boost regression notification (2005-11-02 [HEAD])
by Douglas Gregor 02 Nov '05

02 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-02T06:00:20Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 299 failures in 13 libraries: bind (12) concept_check (12) graph (2) io (1) mpl (1) serialization (30) spirit (8) thread (4) tr1 (147) tuple (1) type_traits (58) typeof (18) xpressive (5) |bind| bind_dm3_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 bind_stateful_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_array: gcc-2.95.3-linux std_test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 std_test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_function: gcc-2.95.3-linux std_test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_hash: gcc-2.95.3-linux std_test_mem_fn: gcc-2.95.3-linux std_test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_random: gcc-2.95.3-linux std_test_reference_wrapper: gcc-2.95.3-linux std_test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_functional: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_memory: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tr1_add_const_test: gcc-2.95.3-linux tr1_add_cv_test: gcc-2.95.3-linux tr1_add_pointer_test: gcc-2.95.3-linux tr1_add_reference_test: gcc-2.95.3-linux tr1_add_volatile_test: gcc-2.95.3-linux tr1_aligned_storage_test: gcc-2.95.3-linux tr1_alignment_of_test: gcc-2.95.3-linux tr1_extent_test: gcc-2.95.3-linux tr1_has_nothrow_assign_test: gcc-2.95.3-linux tr1_has_nothrow_constr_test: gcc-2.95.3-linux tr1_has_nothrow_copy_test: gcc-2.95.3-linux tr1_has_trivial_assign_test: gcc-2.95.3-linux tr1_has_trivial_constr_test: gcc-2.95.3-linux tr1_has_trivial_copy_test: gcc-2.95.3-linux tr1_has_trivial_destructor_test: gcc-2.95.3-linux tr1_has_virtual_destructor_test: gcc-2.95.3-linux tr1_is_abstract_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin tr1_is_arithmetic_test: gcc-2.95.3-linux tr1_is_array_test: gcc-2.95.3-linux tr1_is_base_of_test: gcc-2.95.3-linux tr1_is_class_test: gcc-2.95.3-linux tr1_is_compound_test: gcc-2.95.3-linux tr1_is_const_test: gcc-2.95.3-linux tr1_is_convertible_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_empty_test: gcc-2.95.3-linux tr1_is_enum_test: gcc-2.95.3-linux tr1_is_floating_point_test: gcc-2.95.3-linux tr1_is_function_test: gcc-2.95.3-linux tr1_is_fundamental_test: gcc-2.95.3-linux tr1_is_integral_test: gcc-2.95.3-linux tr1_is_member_func_test: gcc-2.95.3-linux tr1_is_member_obj_test: gcc-2.95.3-linux tr1_is_member_pointer_test: gcc-2.95.3-linux tr1_is_object_test: gcc-2.95.3-linux tr1_is_pod_test: gcc-2.95.3-linux tr1_is_pointer_test: gcc-2.95.3-linux tr1_is_polymorphic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_reference_test: gcc-2.95.3-linux tr1_is_same_test: gcc-2.95.3-linux tr1_is_scalar_test: gcc-2.95.3-linux tr1_is_signed_test: gcc-2.95.3-linux tr1_is_union_test: gcc-2.95.3-linux tr1_is_unsigned_test: gcc-2.95.3-linux tr1_is_void_test: gcc-2.95.3-linux tr1_is_volatile_test: gcc-2.95.3-linux tr1_rank_test: gcc-2.95.3-linux tr1_remove_all_extents_test: gcc-2.95.3-linux tr1_remove_const_test: gcc-2.95.3-linux tr1_remove_cv_test: gcc-2.95.3-linux tr1_remove_extent_test: gcc-2.95.3-linux tr1_remove_pointer_test: gcc-2.95.3-linux tr1_remove_reference_test: gcc-2.95.3-linux tr1_remove_volatile_test: gcc-2.95.3-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

[parameter] - catching accidental duplicate parameters at compile time
by Daniel Earwicker 02 Nov '05

02 Nov '05

To take the first code snippet from the tutorial: new_window("alert", width=10, titlebar=false); Suppose the user accidentally does this: new_window("alert", width=10, titlebar=false, width=2); In the current version of the library this compiles, and by examining the source of the library we can discover that one of the values for 'width' will be used and the other discarded (working out which is left as an exercise for the reader.) It would be nice if this was caught at compile time - especially if the parameter "values" are complex expression templates, making it hard to spot the problem at first glance. One implementation would be to add a recursive metafunction to the body of arg_list: template<class SAME_AS> struct find_duplicates { enum { value = (boost::is_same<SAME_AS, key_type>::value || Next::template find_duplicates<SAME_AS>::value) }; }; BOOST_STATIC_ASSERT(!(Next::template find_duplicates<key_type>::value)); And a terminator to empty_arg_list: template<class SAME_AS> struct find_duplicates { enum { value = false }; }; So an arg_list instantiation will not compile if it adds itself to the front of a list that already contains an arg_list entry using the same keyword type. Hope this is worthwhile. --Daniel.

2 1

[filesystem] and 1.33.1 and windows
by Russell Hind 02 Nov '05

02 Nov '05

Given that filesystem can't be used in MSVC and Borland as a dll, why not completely disable filesystem dll builds and force static linking of the lib? This would stop people spending ages finding out why passing filesystem::native fails when you use a dll build. Could be done for 1.33.1? Cheers Russell

1 0

[ublas] equals(matrix<int>, matrix<int>) causes abort
by David Cameron 02 Nov '05

02 Nov '05

I've been writing some code to serialize and deserialize boost::numeric::ublas::matrixs. While writing unit tests for it I found out about the boost::numeric::ublas::equals function in matrix_assign.hpp. I was relieved, because I had previously been using a templated function to compare matrices. Unfortunately, it doesn't work for me with matrix<int>s. Consider the following cppunit test code: void testMatrixEqualsOperator() { using namespace boost::numeric::ublas; matrix<double> test; test.resize(3,3); CPPUNIT_ASSERT( equals(test,test) ); matrix<int> test1; test.resize(4,4); CPPUNIT_ASSERT( equals(test1,test1) ); } The first four lines work. Adding the next three lines causes the unit tests to fail with an Abort. This is not the standard way CppUnit records a failed test, it must be something failing inside the call to equals(). Previous messages referring to the equals() function argued that it wasn't ready for use because there was rarely a need to compare matrices in real applications. I would argue that it should be working as intended, if only to allow for proper unit testing of code that uses matrices. Here is the function I have been using instead. It works well for me with doubles and ints. Although, I imagine it is not particularly fast. E is for Element. template<class E> bool areMatricesEqual( boost::numeric::ublas::matrix<E> lhs, boost::numeric::ublas::matrix<E> rhs) { using boost::numeric::ublas; if (&lhs == &rhs) return true; if (lhs.size1() != rhs.size1()) return false; if (lhs.size2() != rhs.size2()) return false; typename matrix<E>::iterator1 l(lhs.begin1()); typename matrix<E>::iterator1 r(rhs.begin1()); while (l != lhs.end1()) { if (*l != *r) return false; ++l; ++r; } return true; } I am using gcc-3.3 on ubuntu-5.04 running on an AthlonXP. I'd be happy to provide any more info to help track down the bug. Assuming it is one. -- David Cameron University of British Columbia http://bar.psych.ubc.ca/People/Dave.html

1 0

License blanket permissions
by David Abrahams 02 Nov '05

02 Nov '05

Doh! When we were getting permission from library authors to put the Boost License on their works, we forgot to get permission to upgrade the license, if and when there is ever a 2.0 revision (or a 1.1). There's no forseeable need to change the Boost license, but we hope this software will have a longer-than-usual lifespan and unforseen events always come up eventually. So, we're going to begin a project to collect authors' permission to upgrade the license on their work, as necessary. Naturally any new license would conform to the Boost license requirements, and so would be substantially similar in spirit to the one we have now. -- Dave Abrahams Boost Consulting www.boost-consulting.com

3 2

Re: [boost] [1.33.1 Beta] Release is imminent
by BRIDGES Dick 02 Nov '05

02 Nov '05

Maybe we should wait until Thursday or Friday if we can. Regards, Dick "Multithreading is just one damn thing after, before, or simultaneous with another." Scott Meyers and Andrei Alexandrescu > -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of Doug Gregor > Sent: Tuesday, November 01, 2005 10:20 AM > To: boost(a)lists.boost.org > Subject: [boost] [1.33.1 Beta] Release is imminent > > > We now have zero failures on the RC_1_33_0 branch. The > RC_1_33_0 is now > closed for all commits: write to me *directly* if there is something > that absolutely must go into the 1.33.1 release. I will be > rolling the > release tarballs shortly. > > Doug > > On Nov 1, 2005, at 12:00 PM, Douglas Gregor wrote: > > > Boost regression test failures > > ------------------------------ > > Report time: 2005-11-01T14:47:09Z > > > > This report lists all regression test failures on release platforms. > > > > Detailed report: > > > > http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/ > > developer/issues.html > > > > 0 failure in 0 library: > > > > _______________________________________________ > > Unsubscribe & other changes: > > http://lists.boost.org/mailman/listinfo.cgi/boost > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost >

2 1

Proposal: XML APIs in boost
by Shawn Halpenny 02 Nov '05

02 Nov '05

On 11/1/05, Suman Cherukuri <suman(a)cherukuris.net> wrote: > Xerces has good C++ support. I'm not sure if this discussion is about > extending 'C' based XML parsers like libxml2 and Expat to provide C++ > interface or to have a whole new XML parser within Boost. If it is later, > Why? I agree with Doug Gregor, that something like parsing can be offloaded onto another library like Xerces/libxml2/etc, so I think the value of discussion is in the manipulation and navigation within an XML document. That's where modern C++ techniques could really be applied to great effect. My 2 cents worth regarding the XML libs I've used: Xerces has a bunch of C++ classes ensconced in namespaces, but it feels like a C API dressed up in C++. There is zero in the way of common C++ abstractions for manipulating or accessing a document. It just felt laborious to use--I couldn't escape the thought of "if you're going to write it in C++, how about actually using C++?" With libxml2 I didn't have the "C++ expectations" because it's an all-C API. I still found myself doing the same lower-level node memory-management stuff I had to deal with in Xerces, but I wrote a few brain-dead simple wrapper classes for just the functionality I needed and everything felt so much easier. I suppose the difference is that I expected a whole suite of well-designed wrapper classes along with Xerces and felt let down that they didn't exist. (Plus, I needed RelaxNG schema and XPath support, neither of which Xerces had). -- Shawn Halpenny

1 0

preferred idiom for "occasional properties"
by joel reed 02 Nov '05

02 Nov '05

I've been exploring what a cross platform process library would look like and have a question about whether there is a preferred idiom for what I'll call an occasional property for lack of a better term. Given a process, I'd like to be able to query the parent process. Posix has such a notion, but win32 doesn't. On posix, afaik, every process has a parent except for "init." I can't decide whether I should say class process { public: process parent(); static const process nprocess; // like std::string's npos }; where parent() != nprocess when the process has a parent. or class process { public: typedef std::pair<process,bool> parent_type; parent_type parent(); }; where parent_type.second == true when the process has a parent. I also considered a "parent_iterator", since on posix, you could keep walking backwards up the hierarchy till you get to init, e.g. class parent_iterator; class process { public: parent_iterator parent(); }; but conceptually, I couldn't see a good "end()" Anyone care to offer an idea for the best way to handle this? jr

3 4

Thread-safe Boost.Signals
by Ashok Thirumurthi 01 Nov '05

01 Nov '05

Dear Boost, Doug hinted in the signals FAQ that it is possible to make a thread-safe version of the library. While such a beast may not be in the works, I was wondering if I could write my own layer to serialize calls to the signals library. Typically, we wrap signals using a class as simple as: class NKNEF_ENTRY CImageLoadedEvt : public CImageEvt { typedef boost::signal<void(const ImageLoadData&)> sigNotify_ImageLoaded; public: NKNEF_CALL CImageLoadedEvt(); virtual NKNEF_CALL ~CImageLoadedEvt(); void NKNEF_CALL Connect(const sigNotify_ImageLoaded::slot_type& slot); void NKNEF_CALL Notify(ImageLoadData& data); private: sigNotify_ImageLoaded signal; }; void NKNEF_CALL CImageLoadedEvt::Connect(const CImageLoadedEvt::sigNotify_ImageLoaded::slot_type& slot) { signal.connect(slot); } void NKNEF_CALL CImageLoadedEvt::Notify(ImageLoadData& data) { signal(data); } Can a wrapper be designed to achieve thread-safe use of the signals library? For instance, a critical section could guard concurrent operation of the Connect and Notify methods as well as the destructor... Thanks in advance for your advice, - Ashok Thirumurthi

2 1

[parameter] - arg_list vs. tagged_argument
by Daniel Earwicker 01 Nov '05

01 Nov '05

If width and titlebar are instances of unique specializations of keyword<> then this expression yields an instance of a type that conforms to the "argument pack" concept: (width=10, titlebar=false) However, this expression does not: (width=10) In practise users probably take advantage BOOST_PARAMETER_FUN to declare forwarding functions, so passing a single parameter normally works fine. So this isn't necessarily a problem, but it might cause trouble where users attempt to use a raw argument pack without using boost::parameters<> as a forwarding mechanism. Assignment to a keyword yields a tagged_argument<>, whereas the comma operator yields arg_list<>. The latter is a conforming argument pack. The necessary members could be added to tagged_argument to make it into a conforming argument pack. Or a simpler solution might be to remove tagged_argument altogether and just have the assignment return an arg_list with empty_arg_list as its successor. --Daniel.

1 0

[foreach] something strange is happening ...
by Sascha Seewald 01 Nov '05

01 Nov '05

Hi Boosters! I've been playing around with BOOST_FOREACH a little and got some unexpected results. The following program crashes when I try to iterate a const map with BOOST_FOREACH. That's really strange because for the non-const map everything works fine. Please take a look at the source. What's wrong here? Did I miss something? This is the version in cvs on vc-8_0. Cheers Sascha ----------------------------------------------------------------- <source> #include <boost/foreach.hpp> #include <map> class foo { public: typedef std::map<int, float> map_type; /// return copy of map map_type map() const { return _map; } /// return const copy of map map_type const map_c() const { return _map; } private: map_type _map; }; void main() { foo f; // iterate copy ... ok BOOST_FOREACH( foo::map_type::value_type i, f.map() ) {} // iterate const copy ... crashes here! :-( BOOST_FOREACH( foo::map_type::value_type i, f.map_c() ) {} } </source>

2 3

Boost regression notification (2005-11-01 [HEAD])
by Douglas Gregor 01 Nov '05

01 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-01T06:00:26Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 300 failures in 14 libraries: bind (12) concept_check (12) graph (2) io (1) mpl (1) python (1) serialization (30) spirit (8) thread (4) tr1 (147) tuple (1) type_traits (58) typeof (18) xpressive (5) |bind| bind_dm3_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 bind_stateful_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |python| exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_array: gcc-2.95.3-linux std_test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 std_test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_function: gcc-2.95.3-linux std_test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_hash: gcc-2.95.3-linux std_test_mem_fn: gcc-2.95.3-linux std_test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_random: gcc-2.95.3-linux std_test_reference_wrapper: gcc-2.95.3-linux std_test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_functional: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_memory: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tr1_add_const_test: gcc-2.95.3-linux tr1_add_cv_test: gcc-2.95.3-linux tr1_add_pointer_test: gcc-2.95.3-linux tr1_add_reference_test: gcc-2.95.3-linux tr1_add_volatile_test: gcc-2.95.3-linux tr1_aligned_storage_test: gcc-2.95.3-linux tr1_alignment_of_test: gcc-2.95.3-linux tr1_extent_test: gcc-2.95.3-linux tr1_has_nothrow_assign_test: gcc-2.95.3-linux tr1_has_nothrow_constr_test: gcc-2.95.3-linux tr1_has_nothrow_copy_test: gcc-2.95.3-linux tr1_has_trivial_assign_test: gcc-2.95.3-linux tr1_has_trivial_constr_test: gcc-2.95.3-linux tr1_has_trivial_copy_test: gcc-2.95.3-linux tr1_has_trivial_destructor_test: gcc-2.95.3-linux tr1_has_virtual_destructor_test: gcc-2.95.3-linux tr1_is_abstract_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin tr1_is_arithmetic_test: gcc-2.95.3-linux tr1_is_array_test: gcc-2.95.3-linux tr1_is_base_of_test: gcc-2.95.3-linux tr1_is_class_test: gcc-2.95.3-linux tr1_is_compound_test: gcc-2.95.3-linux tr1_is_const_test: gcc-2.95.3-linux tr1_is_convertible_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_empty_test: gcc-2.95.3-linux tr1_is_enum_test: gcc-2.95.3-linux tr1_is_floating_point_test: gcc-2.95.3-linux tr1_is_function_test: gcc-2.95.3-linux tr1_is_fundamental_test: gcc-2.95.3-linux tr1_is_integral_test: gcc-2.95.3-linux tr1_is_member_func_test: gcc-2.95.3-linux tr1_is_member_obj_test: gcc-2.95.3-linux tr1_is_member_pointer_test: gcc-2.95.3-linux tr1_is_object_test: gcc-2.95.3-linux tr1_is_pod_test: gcc-2.95.3-linux tr1_is_pointer_test: gcc-2.95.3-linux tr1_is_polymorphic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_reference_test: gcc-2.95.3-linux tr1_is_same_test: gcc-2.95.3-linux tr1_is_scalar_test: gcc-2.95.3-linux tr1_is_signed_test: gcc-2.95.3-linux tr1_is_union_test: gcc-2.95.3-linux tr1_is_unsigned_test: gcc-2.95.3-linux tr1_is_void_test: gcc-2.95.3-linux tr1_is_volatile_test: gcc-2.95.3-linux tr1_rank_test: gcc-2.95.3-linux tr1_remove_all_extents_test: gcc-2.95.3-linux tr1_remove_const_test: gcc-2.95.3-linux tr1_remove_cv_test: gcc-2.95.3-linux tr1_remove_extent_test: gcc-2.95.3-linux tr1_remove_pointer_test: gcc-2.95.3-linux tr1_remove_reference_test: gcc-2.95.3-linux tr1_remove_volatile_test: gcc-2.95.3-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

Alternative solution to intermediate results problem of expression templates.
by Korcan Hussein 01 Nov '05

01 Nov '05

Hi I'm not sure if this has already been explored or even in current use but I think I may have come up with an alternative solution to the type deduction of intermediate results from expression templates. Instead of using automatic type erasing technique, take the compile-time parse tree of an intermediate expression and create an exact runtime replica of the expression tree using recursive variant types (using Boost.Variant in C++). The creation of the expression tree can be completely automated. I have tried this myself with promising results. The only (minor) downside is in order to avoid redundant copies of operands the types of the operands must be given but not the structure of the compile-time expression tree itself. Leaf nodes of the recursive variant hold constant references to there elements. I've done quick profile of this against the traditional eager evaluation of overloaded operators and it still is more efficient but tree creation does cost in time slightly. If people are interested I can post code the code for this.

4 20

[serialization] fast array serialization (10x speedup)
by Matthias Troyer 01 Nov '05

01 Nov '05

Hi Robert, Over the past week I got around to doing what I wanted to do for a long time, and implemented an improved serialization of contiguous arrays of fundamental types. The motivation was two-fold: i) to speed up the serialization of large data sets by factors of up to 10 ii) to allow implementation of serialization by MPI The problem with the serialization of large contiguous arrays of fundamental types (be it a C-array, a std::vector, a std::valarray, boost::multi_array, ...) is that the serialization function is called for each (of possible billions) elements, instead of only once for the whole array. I have attached a suite of three benchmark programs and timings I ran on a PowerbookG4 using Apple's version of the gcc-4 compiler. The benchmarks are a) vectortime: reading and writing a std::vector<double> with 10^7 elements to/from a file b) arraytime: reading and writing 1000 arrays double[10000] to/ from a file c) vectortime_memory: reading and writing a std::vector<double> with 10^7 elements to/from a memory buffer The short summary of the benchmarks is that Boost.Serialization is 5-10 times slower than direct reading or writing! With the fast array serialization modifications, discussed below, this slowdown is removed. Note that the codes were compiled with -O2. Without -O2 I have observed another factor of 10 in slowdown in some cases In order to implement the fast array serialization, I made the following changes to the serialization library: i) a new traits class template <class Archive, class Type> has_fast_array_serialization<Archive,Type>; which specifies whether an Archive has fast array serialization for a Type. The default implementation for this traits class is false, so that no change is needed for existing archives. ii) output archives supporting fast array serialization for a given Type T provide an additional member function save_array(T const * address, std:;size_t length); to save a contiguous array of Ts, containing length elements starting at the given address, and a similar function load_array(T * address, std:;size_t length); for input archives iii) serialization of C-arrays and std::vector<T> was changed to use fast array serialization for those archives and types where it is supported. I'm still working on serialization for std::valarray and boost::multi_array using the same features. iv) in addition, to support an MPI serialization archive (which is essentially done but still being tested), and to improve portability of archives, I introduced a new "strong" type BOOST_STRONG_TYPEDEF(std::size_t, container_size_type) for the serialization of the size of a container. The current implementation uses an unsigned int to store the size, which is problematic on machines with 32-bit int but 64 bit size_type . To stay compatible with old archives, the serialization into binary archives converts the size to an unsigned int, but this should be changed to another type, and the file version number bumped up to allow containers with more than 2^32 elements. The second motivation was MPI serialization, for which I need the size type of containers to be a type distinct from any other integer. The explanation is lengthy and I will provide the reason once the MPI archives are finished. v) also the polymporphic archives were changed, by adding save_array and load_array functions. Even for archives not supporting fast array serialization per se this should improve performance, since now only a single virtual function call is required for arrays, instead of one per element. The modifications are on the branch tagged "fast_array_serialization", and I have attached the diffs with respect to the main trunk. I have performed regression tests under darwin, using Apple's version of gcc-4. None of the changes should lead to any incompatibility with archives written with the current version of the serialization library, nor should it break any existing archive implementation. Regarding compatibility with non-conforming compilers the only issue I see is that I have used boost::enable_if to dispatch to either the standard or fast array serialization. We should discuss what to do for compilers that do not support SFINAE. My preferred solution would be to just disable fast array serialization for these compilers, to keep the changed to the code minimal. The other option would be to add another level of indirection and implement the dispatch without using SFINAE. Robert, could you take a look at the modifications, and would it be possibly the merge these modifications with the main trunk once you have finished your work for the 1.33.1 release? Best regards Matthias

6 42

[MPL.Math] rational_part or fractional_part?
by Cromwell Enage 01 Nov '05

01 Nov '05

--- Daryle Walker wrote: > Is BOOST_MPL_MATH_RATIONAL_PART_OF_RATIONAL a > re-statement of the rational number itself? No. > Or is it supposed to be the remainder after taking > out the "whole" part? Yes. > If the latter, then the name should have "FRACTIONAL" > replacing the first "RATIONAL", since "fractional" > and not "rational" better describes a left-over bit. For consistency this part of the macro name is lexically the same as the template name whose specialization the macro creates, i.e. rational_part. > (Rational numbers are a generalization of fractions > that include values with absolute values greater than > one, i.e. a numerator larger than its denominator [in > absolute value].) I have no qualms about changing the name, as long as all interested parties agree. Andy Little? Cromwell D. Enage __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

5 8

[MPL.Math] numeric concepts
by Cromwell Enage 01 Nov '05

01 Nov '05

--- Andy Little wrote: > BTW, I have found that the ability to convert a > rational to an integral_constant if possible is a > useful utility too, though I'm not quite sure > what purists would make of it as the resulting > ::type may be an integral_constant or maybe a > rational constant. I currently call it > "simplify_rational_or_numeric". The resulting ::type > works ok if accessed using the numerator and > denominator functions, and this allows me to make > lists of dimensions using both integral_constants and > rationals. Maybe there is room for such a concept as > an "mpl rational or numeric concept"? In my yet-to-be-submitted documentation, I have the following numeric metatype hierarchy: Numeric Constant | +--Real Numeric Constant | | | +--Discrete Constant--Bitwise Constant | | | | | | +--Integral Constant------+ | | | | | | +--Big Integral Constant--+ | | | +--Continuous Constant | | | +--Rational Constant | | | +--Mixed Numeric Constant | +--Complex Numeric Constant Each concept is defined in terms of the metafunctions that can operate on it, and their semantics. In this scheme, both Integral Constants and Rational Constants are Real Numeric Constants. Not only do the arithmetic metafunctions (negate, plus, minus, times, divides), a few comparison metafunctions (equal_to, not_equal_to), and a few numeric metafunctions (is_zero, zero, real_part, imaginary_part) work on them as they do on other Numeric Constants; but all the other comparison metafunctions (less, greater, less_equal, greater_equal) and all the other numeric metafunctions (is_negative, abs, numerator, denominator, whole_part, fractional_part) work on them as well. A few metafunctions have different semantics for Discrete Constants; e.g. the numerator or whole_part of an Integral Constant is itself, its denominator is always one, and its fractional_part is always zero. To obtain the corresponding run-time values, use the runtime_value facility, which is required to operate on all Numeric Constants. Let me know of any details that need to be fleshed out for you. Cromwell D. Enage __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com

2 2

Re: [boost] VC++ 7.1 build options lead to AV
by Ashok Thirumurthi 01 Nov '05

01 Nov '05

> > Ashok Thirumurthi wrote: > > Dear Boost, > > > > The following call stack leads to an access violation when I link a VC 7.1 DLL > > to the release build of the boost signals 1_33_0 DLL. In comparison, > > there is no access violation when I link to the debug build of the same > > library. Similarly, when I add the signals source to my own release > > DLL, there is no access violation. I attempted to disable all compiler > > optimizations in msvc.jam as follows. However, after running bjam -a > > in signals\build and installing the output, the AV still occurs. > > You were commenting out BBv2 code. Boost.Signals is being build with > BBv1 (if you were building it from the boost root), use "bjam -a --v2" > to build with BBv2. Also, you can use: > > bjam -a --v2 optimization=off > > to turn off the optimization? > Thanks. Disabling all optimizations prevents the access violation. > > How can I alter the release build to avoid the access violation? > > > > Access violation reading location 0x00000004 > > (*((k2).content)).__vfptr is 0x00000000 > > > > bool operator()(const any& k1, const any& k2) const > > { > > if (k1.type() == typeid(front_type)) > > return !(k2.type() == typeid(front_type)); > > if (k1.type() == typeid(back_type)) > > return false; > > > >> if (k2.type() == typeid(front_type)) > > This looks to be an issue with either Boost.Any or your code. What is > any::type() returning? Actually, the () operator is crashing with the access violation. When I run without optimizations, k1.type is front_type and k2.type is back_type. If I optimize for speed (/O2), k1.content is null and k2.content.__vfptr is null. So, type() cannot be evaluated. If I optimize for size (/O1), I observe an invalid lock sequence exception (0xC000001E) when constructing a _Tree_ptr. > Have you made sure that RTTI is enabled for everything (including your > own project -- is there a difference in the vcproj Configurations?) Yes. > > Are you doing something in the Debug version that is not in the Release > version? > > Are you linking with the right variant of the boost libraries? Is there > a conflict with the run-time library being used? I can reproduce the problem and the work-around by compiling the boost source into a DLL using a VC++ 7.1 project. Initially, I had used the bjam scripts without any modification after installing the full 1_33 source. I was able to reproduce the problem with boost 1_32. However, I'm not sure how to determine if a conflict exists. Thanks to your advice regarding bjam, I have a work-around in hand, - Ashok > > - Reece > > > > ------------------------------ > > Message: 4 > Date: Sat, 29 Oct 2005 10:43:59 +0100 > From: "Paul A Bristow" <pbristow(a)hetp.u-net.com> > Subject: Re: [boost] Documentation Wizard > To: <boost(a)lists.boost.org> > Message-ID: <E1EVnFw-0007Bf-Oz(a)he304war.uk.vianw.net> > Content-Type: text/plain; charset="us-ascii" > > > > | -----Original Message----- > | From: boost-bounces(a)lists.boost.org > | [mailto:boost-bounces@lists.boost.org] On Behalf Of Rob Stewart > | Sent: 27 October 2005 23:21 > | To: boost(a)lists.boost.org > | Subject: [boost] Documentation Wizard > | > | Quite some time ago, Dave Abrahams announced that I was the new > | Boost Documentation Wizard. I said I'd write something on the > | subject and that is long overdue. Herewith, I describe what I > | think the DocWiz should do and what is needed from volunteers to > | make it happen. That is, I'm trying to document the new DocWiz > | role and solicit your help. > > My first impression is that this is a bit over-bureaucratic. You obviously > need this sort of style managing 8 offspring ;-) , but Boosters are all > volunteers and we have to be greatful for all the help we can get. > > Authors are severely handicapped when writing documentation by knowing too > much. > > And they are often exhausted by the process of getting the code to work on > the myriad of inconsistent platforms and versions. > > So _any_ documentation editing is likely to be an improvement. > > So I think you should just ask for someone (usually only one - we don't have > _common_ tools for handling versioning and changes well) willing to > contribute to editing each library. The code author and the editor will have > to try to agree: only if they are uncertain should theygo out to the wider > Boost audience. > > Since I have the advantage of having English as my first language (and not > the corrupted version of those renegage ex-colonials ;-), and I have enough > knowledge of other languages to greatly admire those whose first language is > not English struggling with the erudite esoteric elite Boost discussions, I > may offer to edit some documentation. > > HTH > > Paul > > PS And I've read Eats, Shoots and Leaves. > > -- > Paul A Bristow > Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB > Phone and SMS text +44 1539 561830, Mobile and SMS text +44 7714 330204 > mailto: pbristow(a)hetp.u-net.com www.hetp.u-net.com > > > > > > ------------------------------ > > Message: 5 > Date: Sat, 29 Oct 2005 12:01:29 +0100 > From: "Marcin Kalicinski" <kalita(a)poczta.onet.pl> > Subject: [boost] How to run boost regressions? > To: boost(a)lists.boost.org > Message-ID: <djvkq7$ej5$1(a)sea.gmane.org> > > Hi, > > How can I run boost regression tests at home? > > cheers, > Marcin > > > > > > ------------------------------ > > Message: 6 > Date: Sat, 29 Oct 2005 05:57:41 -0700 > From: "SourceForge.net" <noreply(a)sourceforge.net> > Subject: [boost] [Boost-bugs] [ boost-Bugs-1341560 ] crach build bjam > from mingw 3.4.4 > To: noreply(a)sourceforge.net > Message-ID: <E1EVqHF-00048m-K1(a)sc8-sf-web2.sourceforge.net> > Content-Type: text/plain; charset="ISO-8859-1" > > Bugs item #1341560, was opened at 2005-10-29 19:57 > Message generated for change (Tracker Item Submitted) made by Item Submitter > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1341560&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: Alexandr Zamaraev (shura_zam) > Assigned to: Nobody/Anonymous (nobody) > Summary: crach build bjam from mingw 3.4.4 > > Initial Comment: > OS:Windows XP pro rus + sp2 > gcc: (GCC) 3.4.4 (mingw special) > ld: GNU ld version 2.16.91 20050827 > Source: latest csv > > Command line: > >build.bat mingw > Output (last 3 line): > don't know how to make mingw > ...found 1 target... > ...can't find 1 target... > > ---------------------------------------------------------------------- > > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1341560&group_… > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. > Get Certified Today * Register for a JBoss Training Course > Free Certification Exam for All Training Attendees Through End of 2005 > Visit http://www.jboss.com/services/certification for more information > _______________________________________________ > Boost-bugs mailing list > Boost-bugs(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/boost-bugs > > > ------------------------------ > > Message: 7 > Date: Sat, 29 Oct 2005 06:12:26 -0700 > From: "SourceForge.net" <noreply(a)sourceforge.net> > Subject: [boost] [Boost-bugs] [ boost-Bugs-1341568 ] crach build bjam > from mingw 3.4.4 with python > To: noreply(a)sourceforge.net > Message-ID: <E1EVqVW-0005Zb-Rw(a)sc8-sf-web1.sourceforge.net> > Content-Type: text/plain; charset="ISO-8859-1" > > Bugs item #1341568, was opened at 2005-10-29 20:12 > Message generated for change (Tracker Item Submitted) made by Item Submitter > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1341568&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: Alexandr Zamaraev (shura_zam) > Assigned to: Nobody/Anonymous (nobody) > Summary: crach build bjam from mingw 3.4.4 with python > > Initial Comment: > OS: Windows XP pro rus + sp2 > gcc: (GCC) 3.4.4 (mingw special) > ld: GNU ld version 2.16.91 20050827 > Python: Python 2.4.2 > Source: latest csv > > I try build bjam with python. > Bat I have crach in linking. > > Command line: > >bjam -f build.jam --toolset=mingw > --with-python=C:\Lang\Python24 > > Output (latest 8 lines) > C:\TEMP\Shura/ccaSyaaa.o:builtins.c:(.text+0x334e): > undefined reference to `_imp__PyCallable_Check' > C:\TEMP\Shura/ccaSyaaa.o:builtins.c:(.text+0x337c): > undefined reference to `_imp___Py_NoneStruct' > collect2: ld returned 1 exit status > > "gcc" -o bin.ntx86\bjam.exe -DNDEBUG > -DOPT_HEADER_CACHE_EXT -DOPT_GRAPH_DEBUG_EXT > -DOPT_SEMAPHORE -DOPT_FIX_TARGET_VARIABLES_EXT > -DOPT_IMPROVED_PATIENCE_EXT -DNT -DYYSTACKSIZE=5000 > -DHAVE_PYTHON -s -O3 -finline-functions > -IC:\Lang\Python24\include > "C:\Lang\Python24\libs\python24.lib" command.c > compile.c debug.c expand.c glob.c hash.c hcache.c > headers.c hdrmacro.c jam.c jambase.c jamgram.c lists.c > make.c make1.c newstr.c option.c parse.c regexp.c > rules.c scan.c search.c subst.c w32_getreg.c > timestamp.c variable.c modules.c strings.c filesys.c > builtins.c pwd.c class.c native.c modules/set.c > modules/path.c modules/regex.c modules/property-set.c > modules/sequence.c modules/order.c execnt.c filent.c > pathunix.c > > ...failed [COMPILE] bin.ntx86\bjam.exe... > ...failed updating 1 target... > > ---------------------------------------------------------------------- > > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1341568&group_… > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. > Get Certified Today * Register for a JBoss Training Course > Free Certification Exam for All Training Attendees Through End of 2005 > Visit http://www.jboss.com/services/certification for more information > _______________________________________________ > Boost-bugs mailing list > Boost-bugs(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/boost-bugs > > > ------------------------------ > > Message: 8 > Date: Sat, 29 Oct 2005 09:40:28 -0500 > From: Douglas Gregor <doug.gregor(a)gmail.com> > Subject: Re: [boost] How to run boost regressions? > To: boost(a)lists.boost.org > Message-ID: <66D002ED-12FC-40F7-A0AC-BD3AE3A8CA0C(a)cs.indiana.edu> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > > On Oct 29, 2005, at 6:01 AM, Marcin Kalicinski wrote: > > How can I run boost regression tests at home? > > There are some instructions here: > > http://www.boost.org/tools/regression/xsl_reports/runner/ > instructions.html > > Doug > > > > ------------------------------ > > Message: 9 > Date: Sat, 29 Oct 2005 09:51:08 -0500 > From: Douglas Gregor <doug.gregor(a)gmail.com> > Subject: Re: [boost] [GCC 2.95.3] Boost regression notification > (2005-10-28 [HEAD]) > To: boost(a)lists.boost.org > Message-ID: <C805154E-5675-42B4-A0D9-2F42C8920BF1(a)cs.indiana.edu> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > > On Oct 28, 2005, at 5:11 PM, Beman Dawes wrote: > > A lot of these failures are for gcc-2.95.3-linux. Do we care enough > > about > > 2.95.3 nowadays to consider it a release platform? > > I vageuely remember trying to kill GCC 2.95.3 support at one point, > but was convinced otherwise. We could just mark it as unusable on new > libraries/tests that support it but retain backward compatibility on > those libraries that do. > > Doug > > > ------------------------------ > > Message: 10 > Date: Sat, 29 Oct 2005 17:04:16 +0100 > From: "John Maddock" <john(a)johnmaddock.co.uk> > Subject: Re: [boost] [range][1.33.1] last few regressions. > To: <boost(a)lists.boost.org> > Message-ID: <015001c5dca2$7118cab0$6f2e0d52@fuji> > Content-Type: text/plain; format=flowed; charset="iso-8859-1"; > reply-type=original > > > In that case we might as well just roll-back the changes from the RC > > branch to > > the main branch. > > There haven't been any changes to the test itself, and the only changes in > the headers appear to be: > http://cvs.sourceforge.net/viewcvs.py/boost/boost/boost/range/end.hpp?r1=1.… > and related changes. > > I'd still rather see this fixed than just rolled back (I presume these > changes were in there for a reason?), or we could disable them for broken > compilers if that works (but we need to know why they were in there in the > first place, this could be a fix for VC6/7 for all I know). > > BTW I don't have a Boost source tree (or compiler) to work with at present > to test this out, since I've just replaced my hard drive! > > Hopefully this narrows the problem down a bit? > > John. > > > > ------------------------------ > > Message: 11 > Date: Sat, 29 Oct 2005 12:24:53 -0400 > From: David Abrahams <dave(a)boost-consulting.com> > Subject: Re: [boost] [GCC 2.95.3] Boost regression notification > (2005-10-28 [HEAD]) > To: boost(a)lists.boost.org > Message-ID: <uy84cl296.fsf(a)boost-consulting.com> > Content-Type: text/plain; charset=us-ascii > > Douglas Gregor <doug.gregor(a)gmail.com> writes: > > > On Oct 28, 2005, at 5:11 PM, Beman Dawes wrote: > >> A lot of these failures are for gcc-2.95.3-linux. Do we care enough > >> about > >> 2.95.3 nowadays to consider it a release platform? > > > > I vageuely remember trying to kill GCC 2.95.3 support at one point, > > but was convinced otherwise. We could just mark it as unusable on new > > libraries/tests that support it but retain backward compatibility on > ^ > don't?? > > > those libraries that do. > > If not "don't," how will we know we're retaining backward > compatibility? > > -- > Dave Abrahams > Boost Consulting > www.boost-consulting.com > > > > ------------------------------ > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost > > End of Boost Digest, Vol 1260, Issue 1 > ************************************** >

1 0

Re: [boost] [range][1.33.1] last few regressions.
by boost.regex＠virgin.net 31 Oct '05

31 Oct '05

>I need to spend some more time on the range library before I feel>comfortable about releasing it together with boost.foreach.>I need to change the concept requirements and update the docs and won't have>time until the weekend.Understood, but please remember we're talking about patching the 1.33 release source here, *not* a new updated version: that's a different thing entirely.John.

4 7

Boost regression notification (2005-10-30 [RC_1_33_0])
by Douglas Gregor 31 Oct '05

31 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-30T14:55:09Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 8 failures in 4 libraries: date_time (1) filesystem (2) range (3) serialization (2) |date_time| testtz_database: intel-win32-8_1 |filesystem| operations_test: intel-win32-8_1 operations_test_dll: intel-win32-8_1 |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_demo_xml_load: intel-win32-8_1 test_shared_ptr_132_text_warchive: intel-win32-8_1

6 7

What the?
by Dan McLeran 31 Oct '05

31 Oct '05

Yesterday, I tried upgrading from Boost 1.30 to 1.33 and I got the weirdest reaction from my linker. Some background: I am using MSVC6SP6; The code in question is a dll that runs under PharLap 9.1. I am linking against libcmt as well as a lib called cellexe.lib, which provides all of the C runtime stuff and PharLap-specific OS stuff. With Boost 1.30, everything compiles and links just peachy. When I pointed the project at Boost 1.33, I had to make a couple of small code changes: 1. I had to change boost::mpl::apply_if to boost::mpl::eval_if. 2. I had to stop using TrivialIteratorConcept and switched to ForwardIteratorConcept or RandomAccessIteratorConcept. That's really the only code changes I can think of but now my linker gives me a bunch of warnings and 1 error message, which is what's really killing me: Linking... LIBCMT.lib(typinfo.obj) : error LNK2005: "const type_info::`vftable'" (??_7type_info@@6B@) already defined in cellexe.lib(Cellexe.exe) LIBCMT.lib(strtol.obj) : error LNK2005: _strtoul already defined in cellexe.lib(Cellexe.exe) LIBCMT.lib(chkstk.obj) : error LNK2005: __chkstk already defined in cellexe.lib(Cellexe.exe) LIBCMT.lib(xtoa.obj) : error LNK2005: __ultoa already defined in cellexe.lib(Cellexe.exe) LIBCMT.lib(atox.obj) : error LNK2005: _atoi already defined in cellexe.lib(Cellexe.exe) LIBCMT.lib(typinfo.obj) : warning LNK4006: "const type_info::`vftable'" (??_7type_info@@6B@) already defined in cellexe.lib(Cellexe.exe); second definition ignored LIBCMT.lib(strtol.obj) : warning LNK4006: _strtoul already defined in cellexe.lib(Cellexe.exe); second definition ignored LIBCMT.lib(chkstk.obj) : warning LNK4006: __chkstk already defined in cellexe.lib(Cellexe.exe); second definition ignored LIBCMT.lib(xtoa.obj) : warning LNK4006: __ultoa already defined in cellexe.lib(Cellexe.exe); second definition ignored LIBCMT.lib(atox.obj) : warning LNK4006: _atoi already defined in cellexe.lib(Cellexe.exe); second definition ignored Creating library PharLapRelease/Devo.lib and object PharLapRelease/Devo.exp LIBCMT.lib(crt0.obj) : error LNK2001: unresolved external symbol _main PharLapRelease/Devo.dll : fatal error LNK1120: 1 unresolved externals Error executing link.exe. I can't understand why the linker is now searching for _main when the project is a dll and I have all the necessary stuff: .def file, /dll switch, etc. I have compiled and run this dll for literally years when using Boost 1.30. Can anyone think of anything in this Boost library upgrade that could cause this? Keep in mind that I did not change any project setting other than the include directories to point the compiler at the directories containing Boost 1.33 and that I have been using this code along with Boost 1.30 for years.

3 4

Boost regression notification (2005-10-31 [HEAD])
by Douglas Gregor 31 Oct '05

31 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-31T06:00:27Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 290 failures in 14 libraries: concept_check (12) filesystem (2) graph (2) io (1) mpl (1) python (1) serialization (30) spirit (8) thread (4) tr1 (147) tuple (1) type_traits (58) typeof (18) xpressive (5) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 |filesystem| operations_test: intel-win32-9_0 operations_test_dll: intel-win32-9_0 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |python| exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_array: gcc-2.95.3-linux std_test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 std_test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_function: gcc-2.95.3-linux std_test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_hash: gcc-2.95.3-linux std_test_mem_fn: gcc-2.95.3-linux std_test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_random: gcc-2.95.3-linux std_test_reference_wrapper: gcc-2.95.3-linux std_test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_functional: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_memory: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tr1_add_const_test: gcc-2.95.3-linux tr1_add_cv_test: gcc-2.95.3-linux tr1_add_pointer_test: gcc-2.95.3-linux tr1_add_reference_test: gcc-2.95.3-linux tr1_add_volatile_test: gcc-2.95.3-linux tr1_aligned_storage_test: gcc-2.95.3-linux tr1_alignment_of_test: gcc-2.95.3-linux tr1_extent_test: gcc-2.95.3-linux tr1_has_nothrow_assign_test: gcc-2.95.3-linux tr1_has_nothrow_constr_test: gcc-2.95.3-linux tr1_has_nothrow_copy_test: gcc-2.95.3-linux tr1_has_trivial_assign_test: gcc-2.95.3-linux tr1_has_trivial_constr_test: gcc-2.95.3-linux tr1_has_trivial_copy_test: gcc-2.95.3-linux tr1_has_trivial_destructor_test: gcc-2.95.3-linux tr1_has_virtual_destructor_test: gcc-2.95.3-linux tr1_is_abstract_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin tr1_is_arithmetic_test: gcc-2.95.3-linux tr1_is_array_test: gcc-2.95.3-linux tr1_is_base_of_test: gcc-2.95.3-linux tr1_is_class_test: gcc-2.95.3-linux tr1_is_compound_test: gcc-2.95.3-linux tr1_is_const_test: gcc-2.95.3-linux tr1_is_convertible_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_empty_test: gcc-2.95.3-linux tr1_is_enum_test: gcc-2.95.3-linux tr1_is_floating_point_test: gcc-2.95.3-linux tr1_is_function_test: gcc-2.95.3-linux tr1_is_fundamental_test: gcc-2.95.3-linux tr1_is_integral_test: gcc-2.95.3-linux tr1_is_member_func_test: gcc-2.95.3-linux tr1_is_member_obj_test: gcc-2.95.3-linux tr1_is_member_pointer_test: gcc-2.95.3-linux tr1_is_object_test: gcc-2.95.3-linux tr1_is_pod_test: gcc-2.95.3-linux tr1_is_pointer_test: gcc-2.95.3-linux tr1_is_polymorphic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_reference_test: gcc-2.95.3-linux tr1_is_same_test: gcc-2.95.3-linux tr1_is_scalar_test: gcc-2.95.3-linux tr1_is_signed_test: gcc-2.95.3-linux tr1_is_union_test: gcc-2.95.3-linux tr1_is_unsigned_test: gcc-2.95.3-linux tr1_is_void_test: gcc-2.95.3-linux tr1_is_volatile_test: gcc-2.95.3-linux tr1_rank_test: gcc-2.95.3-linux tr1_remove_all_extents_test: gcc-2.95.3-linux tr1_remove_const_test: gcc-2.95.3-linux tr1_remove_cv_test: gcc-2.95.3-linux tr1_remove_extent_test: gcc-2.95.3-linux tr1_remove_pointer_test: gcc-2.95.3-linux tr1_remove_reference_test: gcc-2.95.3-linux tr1_remove_volatile_test: gcc-2.95.3-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

[Boost-bugs] [ boost-Support Requests-1343952 ] object tracking
by SourceForge.net 31 Oct '05

31 Oct '05

Support Requests item #1343952, was opened at 2005-10-31 14:47 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=1343952&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: Luke (jla2w) Assigned to: Nobody/Anonymous (nobody) Summary: object tracking Initial Comment: I upgraded my compiler from VC7 to VC7.1. I rebuilt boost using the new compiler and rebuilt my application. No code relating to use of boost (I use it for it's serialization library) changed, and it worked in VC7, but now I get an assertion in the file oserializer.hpp BOOST_STATIC_ASSERT(check_tracking<T>::value) it says I need to check my object tracking settings...My question is why would it not do this for vc7.0, but it does this for VC7.1? What can I do to remedy this? I use default object tracking settings throughout and I do serialize through pointers a lot. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1343952&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ 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-1343929 ] object tracking
by SourceForge.net 31 Oct '05

31 Oct '05

Support Requests item #1343929, was opened at 2005-10-31 14:31 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=1343929&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: Luke (jla2w) Assigned to: Nobody/Anonymous (nobody) Summary: object tracking Initial Comment: I upgraded my compiler from VC7 to VC7.1. I rebuilt boost using the new compiler and rebuilt my application. No code relating to use of boost (I use it for it's serialization library) changed, and it worked in VC7, but now I get an assertion in the file oserializer.hpp BOOST_STATIC_ASSERT(check_tracking<T>::value) it says I need to check my object tracking settings...My question is why would it not do this for vc7.0, but it does this for VC7.1? What can I do to remedy this? I use default object tracking settings throughout and I do serialize through pointers a lot. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1343929&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[MPL.Math] big_integral and unsigned_big_integral
by Cromwell Enage 31 Oct '05

31 Oct '05

Once again, the latest offering is at <http://boost-consulting.com/vault/>, inside Template Metaprogramming. The ability to write constants like big_integral<positive_sign,1,0,4,8,5,7,6> has returned. In addition, you can also write a constant like unsigned_big_integral<1,0,4,8,5,7,6>, which is equivalent to the above. The two missing pieces wrt full functionality are division and human-readable output. The latter is easier to tackle but will most likely require a corresponding runtime big-integer class. Is anybody (e.g. Christopher Diggins) still working on one? If so, I might use it as a value_type. In a future version I'll probably get rid of positive_sign and negative_sign and just have the user specify '+' or '-'. Peder, I've made changes to the following files: * <boost/mpl/math/numerator.hpp> * <boost/mpl/math/denominator.hpp> * <boost/mpl/math/whole_part.hpp> * <boost/mpl/math/rational_part.hpp> * <boost/mpl/math/big_integral_tag.hpp> * <boost/mpl/math/big_integral_fwd.hpp> * everything in boost/mpl/math/big_integral_ and boost/mpl/math/big_integral_/aux_ * <boost/mpl/math/big_integral.hpp> * <boost/mpl/math/rational.hpp> * <boost/mpl/math/mixed_number.hpp> * <boost/mpl/math/complex_number.hpp> * examples/big_integral.cpp * test/big_integral.cpp Cromwell D. Enage __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

2 3

[mpl::math Rational] type member
by Andy Little 31 Oct '05

31 Oct '05

Hi Cromwell, in <boost/mpl/math/rational.hpp> In the definition for mpl::math::rational would it not be better to make the nested type member using the numerator and denominator rather than the input parameters.eg for: typedef rational<integral_c_<int,2>,integral_c<int,8> >::type type; currently type is a rational<integral_c_<int,2>,integral_c<int,8> > in the second case type is a rational<integral_c_<int,1>,integral_c<int,4> > I believe the second is superior. Can supply a patch if you like ... Secondly, are the next and prior members necessary? IMO they only make sense for integers. Thirdly, It should be noted that there is a <boost/mpl/math/rational_c.hpp> header, but as rational_c is defined in <boost/mpl/math/rational.hpp> I think its now both redundant and confusing. Cheers Andy Little

5 18

Binary files in CVS not marked as binary
by Peter Dimov 30 Oct '05

30 Oct '05

M libs/iostreams/doc/theme/boost_small.png M libs/program_options/test/ucs2.txt M libs/program_options/test/utf8.txt M libs/ptr_container/doc/cboost.gif -- Peter Dimov http://www.pdimov.com

1 0

Boost regression notification (2005-10-29 [RC_1_33_0])
by Douglas Gregor 30 Oct '05

30 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-29T15:30:18Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 11 failures in 4 libraries: date_time (1) parameter (1) range (3) serialization (6) |date_time| testtz_database: intel-win32-8_1 |parameter| tutorial: gcc-2.95.3-linux |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_class_info_load_binary_archive: cw-9_5-darwin test_class_info_load_binary_archive_dll: cw-9_5-darwin test_class_info_load_xml_archive: cw-9_5-darwin test_class_info_load_xml_archive_dll: cw-9_5-darwin test_demo_xml_load: intel-win32-8_1 test_shared_ptr_132_text_warchive: intel-win32-8_1

3 4

Boost regression notification (2005-10-30 [HEAD])
by Douglas Gregor 30 Oct '05

30 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-30T05:00:20Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 288 failures in 13 libraries: concept_check (12) graph (2) io (1) mpl (1) python (1) serialization (30) spirit (8) thread (4) tr1 (147) tuple (1) type_traits (58) typeof (18) xpressive (5) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |python| exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_array: gcc-2.95.3-linux std_test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 std_test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_function: gcc-2.95.3-linux std_test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_hash: gcc-2.95.3-linux std_test_mem_fn: gcc-2.95.3-linux std_test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_random: gcc-2.95.3-linux std_test_reference_wrapper: gcc-2.95.3-linux std_test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_functional: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_memory: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tr1_add_const_test: gcc-2.95.3-linux tr1_add_cv_test: gcc-2.95.3-linux tr1_add_pointer_test: gcc-2.95.3-linux tr1_add_reference_test: gcc-2.95.3-linux tr1_add_volatile_test: gcc-2.95.3-linux tr1_aligned_storage_test: gcc-2.95.3-linux tr1_alignment_of_test: gcc-2.95.3-linux tr1_extent_test: gcc-2.95.3-linux tr1_has_nothrow_assign_test: gcc-2.95.3-linux tr1_has_nothrow_constr_test: gcc-2.95.3-linux tr1_has_nothrow_copy_test: gcc-2.95.3-linux tr1_has_trivial_assign_test: gcc-2.95.3-linux tr1_has_trivial_constr_test: gcc-2.95.3-linux tr1_has_trivial_copy_test: gcc-2.95.3-linux tr1_has_trivial_destructor_test: gcc-2.95.3-linux tr1_has_virtual_destructor_test: gcc-2.95.3-linux tr1_is_abstract_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin tr1_is_arithmetic_test: gcc-2.95.3-linux tr1_is_array_test: gcc-2.95.3-linux tr1_is_base_of_test: gcc-2.95.3-linux tr1_is_class_test: gcc-2.95.3-linux tr1_is_compound_test: gcc-2.95.3-linux tr1_is_const_test: gcc-2.95.3-linux tr1_is_convertible_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_empty_test: gcc-2.95.3-linux tr1_is_enum_test: gcc-2.95.3-linux tr1_is_floating_point_test: gcc-2.95.3-linux tr1_is_function_test: gcc-2.95.3-linux tr1_is_fundamental_test: gcc-2.95.3-linux tr1_is_integral_test: gcc-2.95.3-linux tr1_is_member_func_test: gcc-2.95.3-linux tr1_is_member_obj_test: gcc-2.95.3-linux tr1_is_member_pointer_test: gcc-2.95.3-linux tr1_is_object_test: gcc-2.95.3-linux tr1_is_pod_test: gcc-2.95.3-linux tr1_is_pointer_test: gcc-2.95.3-linux tr1_is_polymorphic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_reference_test: gcc-2.95.3-linux tr1_is_same_test: gcc-2.95.3-linux tr1_is_scalar_test: gcc-2.95.3-linux tr1_is_signed_test: gcc-2.95.3-linux tr1_is_union_test: gcc-2.95.3-linux tr1_is_unsigned_test: gcc-2.95.3-linux tr1_is_void_test: gcc-2.95.3-linux tr1_is_volatile_test: gcc-2.95.3-linux tr1_rank_test: gcc-2.95.3-linux tr1_remove_all_extents_test: gcc-2.95.3-linux tr1_remove_const_test: gcc-2.95.3-linux tr1_remove_cv_test: gcc-2.95.3-linux tr1_remove_extent_test: gcc-2.95.3-linux tr1_remove_pointer_test: gcc-2.95.3-linux tr1_remove_reference_test: gcc-2.95.3-linux tr1_remove_volatile_test: gcc-2.95.3-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

new member to this great list
by Kalyankumar Ramaseshan 30 Oct '05

30 Oct '05

Dear All, My name is Kalyankumar Ramaseshan. I am a new member to this list. Just have downloaded BOOST and have boosted up my C++ libraries in my PC. Its really an wonderful set of libraries. I am proud to be in the list of future C++ group and to use & contribute to this wonderful C++ library of its own class. Wishing BOOST all success. Thank you. Best Regards, R.Kalyankumar

1 0

Is there a way to reliably read an integer from a stream?
by Oliver Kullmann 29 Oct '05

29 Oct '05

Hello, Consider the following basic task: Given an integer variable "n" int n; and an input stream "in" std::istream in; read an integer from in and put it into n. The "solution" in >> n; is not a solution, since according to 27.6.1.2.2 from the C++ standard the locale's num_get<> object is invoked, which according to 22.2.2.1.2 from the C++ standard invokes scanf from the C library, which then according to 7.19.6.2 from the C standard, clause 10, yields undefined behaviour if the number represented in the stream is not representable by the type int. Thus, since "in" represents here user input, and user input shall never yield undefined behaviour, we cannot use "in >> n;". It seems that in the boost library there is no tool to remedy the situation: - Although boost::lexical_cast does not specify which errors are checked and which are not, it seems that lexical_cast just forwards the action to some std::stringstream object, and the same problem as above arises. - Boost::numeric_cast only works with objects of numeric types, and thus does not contribute to the problem of converting a character sequence into an integer. So, it seems, that this fundamental problem is neither addressed by the C++ standard library nor by the Boost library, and thus I have to write a parser etc. myself for the arithmetic types in C++ ? Is this really so?? Oliver P.S. The easiest way to parse the input from in and check for overflow / underflow seems to me to get the sequence of digits into a std::string digits; erase leading zeros, and compare this string to the string std::string ref = boost::lexical_cast<std::string>(std::numerical_limits<int>::max()); In case of overflow: If digits.size() < ref.size(), then fine, if digits.size() > ref.size(), then bad, otherwise we use lexicographical comparison. A convenient design then perhaps is a wrapper class template <typename Int> class safe_wrapper; such that we can use safe_wrapper<int> n; in >> n; if (not in) throw Error;

3 7

Boost regression notification (2005-10-29 [HEAD])
by Douglas Gregor 29 Oct '05

29 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-29T05:00:30Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 300 failures in 14 libraries: concept_check (13) graph (2) io (1) mpl (1) parameter (2) python (1) serialization (36) spirit (8) thread (4) tr1 (147) tuple (1) type_traits (58) typeof (21) xpressive (5) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| efficiency: msvc sfinae: msvc |python| exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_array: gcc-2.95.3-linux std_test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 std_test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_function: gcc-2.95.3-linux std_test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_hash: gcc-2.95.3-linux std_test_mem_fn: gcc-2.95.3-linux std_test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_random: gcc-2.95.3-linux std_test_reference_wrapper: gcc-2.95.3-linux std_test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_functional: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_memory: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tr1_add_const_test: gcc-2.95.3-linux tr1_add_cv_test: gcc-2.95.3-linux tr1_add_pointer_test: gcc-2.95.3-linux tr1_add_reference_test: gcc-2.95.3-linux tr1_add_volatile_test: gcc-2.95.3-linux tr1_aligned_storage_test: gcc-2.95.3-linux tr1_alignment_of_test: gcc-2.95.3-linux tr1_extent_test: gcc-2.95.3-linux tr1_has_nothrow_assign_test: gcc-2.95.3-linux tr1_has_nothrow_constr_test: gcc-2.95.3-linux tr1_has_nothrow_copy_test: gcc-2.95.3-linux tr1_has_trivial_assign_test: gcc-2.95.3-linux tr1_has_trivial_constr_test: gcc-2.95.3-linux tr1_has_trivial_copy_test: gcc-2.95.3-linux tr1_has_trivial_destructor_test: gcc-2.95.3-linux tr1_has_virtual_destructor_test: gcc-2.95.3-linux tr1_is_abstract_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin tr1_is_arithmetic_test: gcc-2.95.3-linux tr1_is_array_test: gcc-2.95.3-linux tr1_is_base_of_test: gcc-2.95.3-linux tr1_is_class_test: gcc-2.95.3-linux tr1_is_compound_test: gcc-2.95.3-linux tr1_is_const_test: gcc-2.95.3-linux tr1_is_convertible_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_empty_test: gcc-2.95.3-linux tr1_is_enum_test: gcc-2.95.3-linux tr1_is_floating_point_test: gcc-2.95.3-linux tr1_is_function_test: gcc-2.95.3-linux tr1_is_fundamental_test: gcc-2.95.3-linux tr1_is_integral_test: gcc-2.95.3-linux tr1_is_member_func_test: gcc-2.95.3-linux tr1_is_member_obj_test: gcc-2.95.3-linux tr1_is_member_pointer_test: gcc-2.95.3-linux tr1_is_object_test: gcc-2.95.3-linux tr1_is_pod_test: gcc-2.95.3-linux tr1_is_pointer_test: gcc-2.95.3-linux tr1_is_polymorphic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_reference_test: gcc-2.95.3-linux tr1_is_same_test: gcc-2.95.3-linux tr1_is_scalar_test: gcc-2.95.3-linux tr1_is_signed_test: gcc-2.95.3-linux tr1_is_union_test: gcc-2.95.3-linux tr1_is_unsigned_test: gcc-2.95.3-linux tr1_is_void_test: gcc-2.95.3-linux tr1_is_volatile_test: gcc-2.95.3-linux tr1_rank_test: gcc-2.95.3-linux tr1_remove_all_extents_test: gcc-2.95.3-linux tr1_remove_const_test: gcc-2.95.3-linux tr1_remove_cv_test: gcc-2.95.3-linux tr1_remove_extent_test: gcc-2.95.3-linux tr1_remove_pointer_test: gcc-2.95.3-linux tr1_remove_reference_test: gcc-2.95.3-linux tr1_remove_volatile_test: gcc-2.95.3-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

Boost regression notification (2005-10-28 [HEAD])
by Douglas Gregor 29 Oct '05

29 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-28T05:00:11Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 304 failures in 16 libraries: concept_check (13) graph (2) io (1) mpl (1) multi_index (1) numeric/conversion (3) parameter (2) python (1) serialization (36) spirit (8) thread (4) tr1 (147) tuple (1) type_traits (58) typeof (21) xpressive (5) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |multi_index| test_iterators: vc-7_1 |numeric/conversion| converter_test: vc-7_1 udt_example_0: vc-7_1 udt_support_test: vc-7_1 |parameter| efficiency: msvc sfinae: msvc |python| exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_array: gcc-2.95.3-linux std_test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 std_test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_function: gcc-2.95.3-linux std_test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_hash: gcc-2.95.3-linux std_test_mem_fn: gcc-2.95.3-linux std_test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_random: gcc-2.95.3-linux std_test_reference_wrapper: gcc-2.95.3-linux std_test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_functional: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_memory: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tr1_add_const_test: gcc-2.95.3-linux tr1_add_cv_test: gcc-2.95.3-linux tr1_add_pointer_test: gcc-2.95.3-linux tr1_add_reference_test: gcc-2.95.3-linux tr1_add_volatile_test: gcc-2.95.3-linux tr1_aligned_storage_test: gcc-2.95.3-linux tr1_alignment_of_test: gcc-2.95.3-linux tr1_extent_test: gcc-2.95.3-linux tr1_has_nothrow_assign_test: gcc-2.95.3-linux tr1_has_nothrow_constr_test: gcc-2.95.3-linux tr1_has_nothrow_copy_test: gcc-2.95.3-linux tr1_has_trivial_assign_test: gcc-2.95.3-linux tr1_has_trivial_constr_test: gcc-2.95.3-linux tr1_has_trivial_copy_test: gcc-2.95.3-linux tr1_has_trivial_destructor_test: gcc-2.95.3-linux tr1_has_virtual_destructor_test: gcc-2.95.3-linux tr1_is_abstract_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin tr1_is_arithmetic_test: gcc-2.95.3-linux tr1_is_array_test: gcc-2.95.3-linux tr1_is_base_of_test: gcc-2.95.3-linux tr1_is_class_test: gcc-2.95.3-linux tr1_is_compound_test: gcc-2.95.3-linux tr1_is_const_test: gcc-2.95.3-linux tr1_is_convertible_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_empty_test: gcc-2.95.3-linux tr1_is_enum_test: gcc-2.95.3-linux tr1_is_floating_point_test: gcc-2.95.3-linux tr1_is_function_test: gcc-2.95.3-linux tr1_is_fundamental_test: gcc-2.95.3-linux tr1_is_integral_test: gcc-2.95.3-linux tr1_is_member_func_test: gcc-2.95.3-linux tr1_is_member_obj_test: gcc-2.95.3-linux tr1_is_member_pointer_test: gcc-2.95.3-linux tr1_is_object_test: gcc-2.95.3-linux tr1_is_pod_test: gcc-2.95.3-linux tr1_is_pointer_test: gcc-2.95.3-linux tr1_is_polymorphic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tr1_is_reference_test: gcc-2.95.3-linux tr1_is_same_test: gcc-2.95.3-linux tr1_is_scalar_test: gcc-2.95.3-linux tr1_is_signed_test: gcc-2.95.3-linux tr1_is_union_test: gcc-2.95.3-linux tr1_is_unsigned_test: gcc-2.95.3-linux tr1_is_void_test: gcc-2.95.3-linux tr1_is_volatile_test: gcc-2.95.3-linux tr1_rank_test: gcc-2.95.3-linux tr1_remove_all_extents_test: gcc-2.95.3-linux tr1_remove_const_test: gcc-2.95.3-linux tr1_remove_cv_test: gcc-2.95.3-linux tr1_remove_extent_test: gcc-2.95.3-linux tr1_remove_pointer_test: gcc-2.95.3-linux tr1_remove_reference_test: gcc-2.95.3-linux tr1_remove_volatile_test: gcc-2.95.3-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

5 5

How to run boost regressions?
by Marcin Kalicinski 29 Oct '05

29 Oct '05

Hi, How can I run boost regression tests at home? cheers, Marcin

2 1

[Boost-bugs] [ boost-Bugs-1341568 ] crach build bjam from mingw 3.4.4 with python
by SourceForge.net 29 Oct '05

29 Oct '05

Bugs item #1341568, was opened at 2005-10-29 20:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1341568&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: Alexandr Zamaraev (shura_zam) Assigned to: Nobody/Anonymous (nobody) Summary: crach build bjam from mingw 3.4.4 with python Initial Comment: OS: Windows XP pro rus + sp2 gcc: (GCC) 3.4.4 (mingw special) ld: GNU ld version 2.16.91 20050827 Python: Python 2.4.2 Source: latest csv I try build bjam with python. Bat I have crach in linking. Command line: >bjam -f build.jam --toolset=mingw --with-python=C:\Lang\Python24 Output (latest 8 lines) C:\TEMP\Shura/ccaSyaaa.o:builtins.c:(.text+0x334e): undefined reference to `_imp__PyCallable_Check' C:\TEMP\Shura/ccaSyaaa.o:builtins.c:(.text+0x337c): undefined reference to `_imp___Py_NoneStruct' collect2: ld returned 1 exit status "gcc" -o bin.ntx86\bjam.exe -DNDEBUG -DOPT_HEADER_CACHE_EXT -DOPT_GRAPH_DEBUG_EXT -DOPT_SEMAPHORE -DOPT_FIX_TARGET_VARIABLES_EXT -DOPT_IMPROVED_PATIENCE_EXT -DNT -DYYSTACKSIZE=5000 -DHAVE_PYTHON -s -O3 -finline-functions -IC:\Lang\Python24\include "C:\Lang\Python24\libs\python24.lib" command.c compile.c debug.c expand.c glob.c hash.c hcache.c headers.c hdrmacro.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c parse.c regexp.c rules.c scan.c search.c subst.c w32_getreg.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c execnt.c filent.c pathunix.c ...failed [COMPILE] bin.ntx86\bjam.exe... ...failed updating 1 target... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1341568&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Boost-bugs] [ boost-Bugs-1341560 ] crach build bjam from mingw 3.4.4
by SourceForge.net 29 Oct '05

29 Oct '05

Bugs item #1341560, was opened at 2005-10-29 19:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1341560&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: Alexandr Zamaraev (shura_zam) Assigned to: Nobody/Anonymous (nobody) Summary: crach build bjam from mingw 3.4.4 Initial Comment: OS:Windows XP pro rus + sp2 gcc: (GCC) 3.4.4 (mingw special) ld: GNU ld version 2.16.91 20050827 Source: latest csv Command line: >build.bat mingw Output (last 3 line): don't know how to make mingw ...found 1 target... ...can't find 1 target... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1341560&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

VC++ 7.1 build options lead to AV
by Ashok Thirumurthi 29 Oct '05

29 Oct '05

Dear Boost, The following call stack leads to an access violation when I link a VC 7.1 DLL to the release build of the boost signals 1_33_0 DLL. In comparison, there is no access violation when I link to the debug build of the same library. Similarly, when I add the signals source to my own release DLL, there is no access violation. I attempted to disable all compiler optimizations in msvc.jam as follows. However, after running bjam -a in signals\build and installing the output, the AV still occurs. # 8.0 deprecates some of the options if ! [ MATCH ^([67].*) : $(version) ] { # flags msvc.compile CFLAGS $(condition)/<optimization>speed : /O2 ; # flags msvc.compile CFLAGS $(condition)/<optimization>space : /O1 ; flags msvc.link.dll MANIFEST : "mt -manifest " ; flags msvc.link.dll OUTPUTRESOURCE : "-outputresource:" ; } else { # flags msvc.compile CFLAGS $(condition)/<optimization>speed : /Ogity /O2 /Gs ; # flags msvc.compile CFLAGS $(condition)/<optimization>space : /Ogisy /O1 /Gs ; } Note that I have a default installation of Visual Studio 2003. How can I alter the release build to avoid the access violation? More information: Access violation reading location 0x00000004 (*((k2).content)).__vfptr is 0x00000000 bool operator()(const any& k1, const any& k2) const { if (k1.type() == typeid(front_type)) return !(k2.type() == typeid(front_type)); if (k1.type() == typeid(back_type)) return false; > if (k2.type() == typeid(front_type)) return false; if (k2.type() == typeid(back_type)) return true; > Colorado.dll!boost::signals::detail::any_bridge_compare<std::less<int>,int>::operator()(const boost::any & k1={...}, const boost::any & k2={...}) Line 54 + 0xc C++ Colorado.dll!boost::detail::function::function_obj_invoker2<boost::signals::detail::any_bridge_compare<std::less<int>,int>,bool,boost::any,boost::any>::invoke(boost::detail::function::any_pointer function_obj_ptr={...}, boost::any a0={...}, boost::any a1={...}) Line 119 + 0x1b C++ boost_signals-vc71-mt-1_33.dll!010a2340() boost_signals-vc71-mt-1_33.dll!010a2c6a() boost_signals-vc71-mt-1_33.dll!010a42be() boost_signals-vc71-mt-1_33.dll!010a4bd0() boost_signals-vc71-mt-1_33.dll!010a4dfc() boost_signals-vc71-mt-1_33.dll!010a5933() Colorado.dll!boost::signal0<bool,boost::last_value<bool>,int,std::less<int>,boost::function<bool __stdcall(void),std::allocator<void> > >::signal0<bool,boost::last_value<bool>,int,std::less<int>,boost::function<bool __stdcall(void),std::allocator<void> > >(const boost::last_value<bool> & c={...}, const std::less<int> & comp={...}) Line 198 + 0x85 C++ ... Do these observations suggest how I might successfully handle this callback from the release boost DLL? Thanks in advance, - Ashok Thirumurthi

2 1

bind/bind_template.hpp + EDG 238 trouble + patch
by Ralf W. Grosse-Kunstleve 28 Oct '05

28 Oct '05

Hi, The changes to boost/bind/bind_template.hpp from 10/25 break the Boost.Python build under IRIX/MIPSpro 7.3.1. The problem is due to a known bug in the old EDG frontend (it is the obscure "ambiguous by inheritance" bug). Attached is a simple patch that restores the Boost.Python build. I've tested the patch on 18 other platforms, incl. Windows, Mac OS X, Tru64 Unix, and a bunch of Linux distributions. If the patch looks reasonable and I get an OK I'd be happy to check it in. Thanks! Cheers, Ralf Index: bind_template.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/bind/bind_template.hpp,v retrieving revision 1.6 diff -u -r1.6 bind_template.hpp --- bind_template.hpp 25 Oct 2005 21:01:41 -0000 1.6 +++ bind_template.hpp 28 Oct 2005 17:28:28 -0000 @@ -38,7 +38,8 @@ BOOST_BIND_RETURN l_(type<result_type>(), f_, a, 0); } -#if !defined(BOOST_NO_FUNCTION_TEMPLATE_ORDERING) +#if !defined(BOOST_NO_FUNCTION_TEMPLATE_ORDERING) \ + && !BOOST_WORKAROUND(__EDG_VERSION__, <= 238) template<class A1> result_type operator()(A1 const & a1) { @@ -66,7 +67,8 @@ BOOST_BIND_RETURN l_(type<result_type>(), f_, a, 0); } -#if !defined(BOOST_NO_FUNCTION_TEMPLATE_ORDERING) +#if !defined(BOOST_NO_FUNCTION_TEMPLATE_ORDERING) \ + && !BOOST_WORKAROUND(__EDG_VERSION__, <= 238) template<class A1, class A2> result_type operator()(A1 const & a1, A2 & a2) { __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

2 2

Boost regression notification (2005-10-28 [RC_1_33_0])
by Douglas Gregor 28 Oct '05

28 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-28T15:01:23Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 59 failures in 4 libraries: parameter (1) range (3) serialization (53) thread (2) |parameter| tutorial: gcc-2.95.3-linux |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_class_info_load_binary_archive: borland-5_6_4 cw-8_3 cw-9_5-darwin gcc-3_4_3-sunos vc-6_5 vc-7_0 test_class_info_load_binary_archive_dll: borland-5_6_4 cw-9_5-darwin gcc-3_4_3-sunos vc-6_5 vc-7_0 test_class_info_load_text_archive: borland-5_6_4 cw-8_3 gcc-3_4_3-sunos vc-6_5 vc-7_0 test_class_info_load_text_archive_dll: borland-5_6_4 gcc-3_4_3-sunos vc-6_5 vc-7_0 test_class_info_load_text_warchive: borland-5_6_4 cw-8_3 gcc-3_4_3-sunos vc-7_0 test_class_info_load_text_warchive_dll: borland-5_6_4 gcc-3_4_3-sunos vc-7_0 test_class_info_load_xml_archive: borland-5_6_4 cw-8_3 cw-9_5-darwin gcc-3_4_3-sunos vc-6_5 vc-7_0 test_class_info_load_xml_archive_dll: borland-5_6_4 cw-9_5-darwin gcc-3_4_3-sunos vc-6_5 vc-7_0 test_class_info_load_xml_warchive: borland-5_6_4 cw-8_3 gcc-3_4_3-sunos vc-6_5 vc-7_0 test_class_info_load_xml_warchive_dll: borland-5_6_4 gcc-3_4_3-sunos vc-6_5 vc-7_0 test_demo_xml_load: borland-5_6_4 gcc-3_4_3-sunos intel-win32-8_1 test_demo_xml_load_dll: borland-5_6_4 gcc-3_4_3-sunos test_shared_ptr_132_text_warchive: intel-win32-8_1 |thread| test_mutex: cw-9_4 test_thread: intel-win32-8_1

1 0

Re: [boost] alignment trouble with boost::optional
by Martin Bonner 28 Oct '05

28 Oct '05

----Original Message---- From: David Abrahams [mailto:dave@boost-consulting.com] Sent: 27 October 2005 12:57 To: boost(a)lists.boost.org Subject: Re: [boost] alignment trouble with boost::optional > Michael Shepanski <mshepanski(a)gmail.com> writes: > >> On 10/26/05, David Abrahams <dave(a)boost-consulting.com> wrote: >>> >>> >>> I think the problem is that type_with_alignment can't find a type >>> that has an alignment of 12. Producing an error in that case is the >>> right behavior. We could add the type whose alignment_of<> is 12 to >>> the reperotoire of types being tested by type_with_alignment... >> >> >> >> Don't we need to be sure that type_with_alignment<> can accept *any* >> number that alignment_of<> produces -- or, conversely, make sure that >> alignment_of<> only produces numbers that type_with_alignment<> can >> accept? (I'm assuming that we want boost::optional to work all the >> time, not just for my example.) > > Sure, that's what we want. Can you figure out *how*? That's the > problem. In summary: 1. alignment_of<T> produces a number that is a multiple of the required alignment. 2. type_with_alignment<> cannot deal with all the numbers that alignment_of<> produces. Does anyone know of any platform (including platforms that are no longer in use), where the alignment requirement was /not/ a power of two? If not, then alignment_of<> "just" needs to eliminate the factors from its result which are not a power of two. (That would also allow us to eliminate the special case for long double under Borland). -- 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

[shmem] New snapshot available: Review Request
by Ion Gaztañaga 28 Oct '05

28 Oct '05

Hi to all! I've just uploaded a new snapshot of Shmem to Boost Vault/Memory folder. Online documentation, as always, is here: http://ice.prohosting.com/newfunk/boost/libs/shmem/doc/html/index.html New features: -> Windows API predeclaration so windows.h include is eliminated. Since Shmem is a header-only library, this change should help compile times. -> Null index type: If you don't need named allocations, and you want some space and compilation time, you can use a null index type instead of paying for an index you don't use. -> New synchronization primitive: named_mutex (Similar to Windows named mutex). -> Doxygen reference error corrections thanks a Boostbook Doxygen patch. There are some slight errors from BoostBook but now it looks much better. -> Improved named object destruction performance with destroy_ptr when using node container based indexes (map_index). Now is O(N) instead of O(logN). -> Decoupled red-black tree algorithms from shmem_tree class so that there is a good base for future shared memory intrusive rb_tree containers. -> Documentation corrections. Open issues, future work and references chapters added. -> Bugfixes. Tested in Windows XP with VC.NET 2003 and Suse 10.0 with gcc 4.0.2. I would like to request a review for Shmem to add it to Boost and I only plan to fix bugs until the review starts. I think there are some open issues in Shmem that should be solved (if Shmem is going to be accepted, of course) during the review. The most important ones are related to Boost Thread and the need of avoiding functionality duplication (scoped_locks, time representation, etc...). I've described them in Open Issues chapter of the documentation. If Shmem is considered good enough for Boost, I would like to work with Boost Thread's users and developers to have a common interface and utilities in thread-shared and process-shared synchronization objects, etc... I started Shmem 11 months ago (and the process of placing STL containers in shared memory many months before) and I would like to thank all who have tested the library, for all their ideas, suggestions and help. Regards, Ion

3 4

Re: [boost] Is there any interest in a library that provides containers with virtual destructors?
by Victor A. Wagner Jr. 28 Oct '05

28 Oct '05

At 10:48 2005-10-27, Matt Calabrese wrote: >On 10/27/05, Victor A. Wagner Jr. <vawjr(a)rudbek.com> wrote: > > > > OK, fix the core language so that I don't have to write the whole > > batch of forwarding functions, AND I get the new ones automatically > > when std::vector gets updated!! > > No??? don't wanna do that? > > then it ISA std::vector<> (or whatever STL collection I choose)!! > > >Don't use an IS-A relationship just because you want to save time typing. >Use an IS-A relationship if IS-A makes sense. If you really always want all >of vector's operations exposed without additional typing, then just >encapsulate it and make it public. If you want the member functions to be a >direct part of the encapsulating class, then use private inheritance and >promote the member functions and types from the vector base class to your >type's public interface with using-delcarations. and that gains me what? a LOT of typing (why the heck isn't there a using class blah; like we have using namespace widget; ??) that needs to be checked.. and possibly modified every time (well ok, once every decade or so) the library is updated. A major maintenance headache just waiting to happen. and I _have_ to make ALL the methods public and ALL the typedefs because I would like to use my collection with ALL of the stuff in <algorithm> and you're never _quite_ sure what an implementation _might_ do or need. It's not that I'm in love with this idea, I'm just saying that it is NOT always bad to inherit from a concrete class that doesn't have a virtual destructor. That's where this all started. I've done it only in a couple places (from standard library things).. mostly to satisfy some programmers who've convinced management that they can't _possibly_ use a string class that doesn't have (pick one... trim, upcase, whatever) and I'm very likely to do it to attempt to normalize the container libraries in the STL as part of an article attempting to shame the committee into making some changes. >-- >-Matt Calabrese >_______________________________________________ >Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

2 1

Re: [boost] Is there any interest in a library that provides cont ainers with virtual destructors?
by Martin Bonner 28 Oct '05

28 Oct '05

----Original Message---- From: Victor A. Wagner Jr. [mailto:vawjr@rudbek.com] Sent: 26 October 2005 15:16 To: boost(a)lists.boost.org; 'boost(a)lists.boost.org' Subject: Re: [boost] Is there any interest in a library that provides cont ainers with virtual destructors? > At 02:51 2005-10-26, Martin Bonner wrote: >> ----Original Message---- >> From: Victor A. Wagner Jr. [mailto:vawjr@rudbek.com] >> Sent: 26 October 2005 05:36 >> To: boost(a)lists.boost.org; boost(a)lists.boost.org >> Subject: Re: [boost] Is there any interest in a library that provides >> containers with virtual destructors? >> >>> At 10:04 2005-10-25, Andy Tompkins wrote: >>>> I have read a few times that people sometimes wish that std::vector >>>> (or other containers) had a virtual destructor. [snip] >>>> This allows one to write something like: >>>> >>>> struct person { >>>> string first_name; >>>> string last_name; >>>> }; >>>> class people : public virtual_vector<person> >>>> { >>>> public: >>>> //extra methods >>>> }; >>>> >>>> Is this useful? >>> >>> unless I mis-read (or mis-understood...far more likely) a lot of >>> books on how C++ works, I don't believe there is any reason for what >>> _you've_ shown to need a virtual destructor. >> >> You have mis-read or mis-understood (or you need better books). >> Consider: virtual_vector<person>* p = new people; > > I guees I wasn't clear.. I was suggesting that virtual_vector has no > need for existence. > >> delete p; >> That invokes undefined behaviour unless virtual_vector<person> has a >> virtual destructor. > > are you suggesting that if it were class people: public > std::vector<person> {.....}; as above the same would be true? > not "in practice", "in theory". Absolutely. See 5.3.5/1 of the standard where this is explicitly called out as undefined behaviour. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

4 8

Re: [boost] Is there any interest in a library that provides cont ainers with virtual destructors?
by Martin Bonner 28 Oct '05

28 Oct '05

----Original Message---- From: Matt Calabrese [mailto:rivorus@gmail.com] Sent: 27 October 2005 06:44 To: boost(a)lists.boost.org Subject: Re: [boost] Is there any interest in a library that provides containers with virtual destructors? > On 10/27/05, Victor A. Wagner Jr. <vawjr(a)rudbek.com> wrote: >> >> indeed, but there is no dynamic type vs static type in the example. > > > If you have a virtual_vector<person>* which points to an instance of > people, and you call delete with that pointer as an operand, you > have undefined behavior unless virtual_vector<person> has a virtual > destructor since virtual_vector<person> is the static type and people > is the dynamic type. Nit: Actually the static type is virtual_vector<person>*, and the dynamic type is people*. (The standard talks about the static and dynamic types of the operand to delete, not the static and dynamic types of the object pointed to by the operand to delete.) (Given the mess I made of the last reference I made to the standard, I shall be interested to see what I have got wrong THIS time!) -- 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 T-Shirts @ Cafe Press
by Jeff Garland 28 Oct '05

28 Oct '05

Hi All - As everyone is probably already aware, we have a new Boost logo that was created by booster Zoltan 'cad' Juhasz. As part of the final logo refinement process, the moderators asked Zoltan if he could create T-Shirts with the new logo. We also felt it was appropriate that Zoltan be the beneficiary of any proceeds associated with the T-Shirts since it was his tireless work that went into the logo and T-Shirt design. With that in mind, I'm delighted to announce that Zoltan worked out some T-Shirt designs and has set up a couple shops at Cafe Press so that people can purchase Boost T-Shirts. - http://www.cafepress.com/boostlibs - http://www.cafepress.com/boostlibsb If you have suggestions or other ideas you can find Zoltan's contact info at: http://people.inf.elte.hu/cad Jeff

1 0

Re: [boost] Is there any interest in a library that provides container
by brangdon＠cix.compulink.co.uk 27 Oct '05

27 Oct '05

In-Reply-To: <1130423747.22962.246152955(a)webmail.messagingengine.com> atompkins(a)fastmail.fm (Andy Tompkins) wrote (abridged): > I have also realized that (for my purposes) I don't require the > ability to delete people from a pointer to its base class > [code skipped] You might consider having wrap_vector inherit privately from std::vector and adding using-declarations rather than forwarding functions. I don't think using composition gains much, given that you are going to inherit from wrap_vector anyway. Using-declarations would be less code, possibly a lower abstraction penalty and would avoid problems with tracking exactly the std vector declarations. > // overload wrap_vector member functions for different behavior That's risky, because there is an implicit conversion from people to wrap_vector<person> and your overloads won't affect the wrap_vector versions. What I think you really want to do is prevent the derived to base conversion. It's a shame this doesn't work: #include <vector> struct Container : public std::vector<int> { typedef std::vector<int> base; private: operator base &(); operator const base &() const; }; void test() { Container *p1 = new Container; Container::base &p2 = *p1; // Shame this compiles. } Maybe it is worth floating in comp.std.c++. -- Dave Harris, Nottingham, UK.

2 1

Re: [boost] Is there any interest in a library that provides container
by brangdon＠cix.compulink.co.uk 27 Oct '05

27 Oct '05

In-Reply-To: <6.2.3.4.2.20051026233845.06694ac0(a)mail.rudbek.com> vawjr(a)rudbek.com (Victor A. Wagner Jr.) wrote (abridged): > OK, fix the core language so that I don't have to write the whole > batch of forwarding functions You can use private inheritance and using-declarations, if that helps. > AND I get the new ones automatically when std::vector gets updated!! That's the controversial part. If you inherit from std::vector it is relatively easy for changes to the std library to break your code. The worst case is when the base class adds a virtual function with the same name as one of your private member functions. You might consider using non-member functions which take a std::vector argument instead. It sounds like you are not adding any data or virtual functions, so your new stuff may not actually need to be member functions? -- Dave Harris, Nottingham, UK.

1 0

Re: [boost] Is there any interest in a library that provides container
by brangdon＠cix.compulink.co.uk 27 Oct '05

27 Oct '05

In-Reply-To: <djpuvk$q3d$1(a)sea.gmane.org> simon(a)hand-multimedia.co.nz (Simon Buchan) wrote (abridged): > > Generally when I've wished for that I've also wished for a few other > > virtual functions. For example, a hook which gets called whenever an > > item is added to the vector [...] > > That's what your class would add, presumably. Yes, but as I understand it, I can't usefully add them by inheriting from the proposed class. This is because, eg, virtual_vector::push_back is not virtual. Users could do: my_vec<int> *p1 = new my_vec; p1->push_back( 0 ); // OK, uses my hook. virtual_vector *p2 = p1; p2->push_back( 0 ); // Silent error, does not use my hook. In my view to be useful a virtual_vector would need lots of virtual methods, not just the destructor. > But when you *do* want to write a vector (or whatever) interface > compliant class, it's a bloody pain to do it for each one you do. I can only report my experience, which is that I've never wanted to do that. > His impl has the benefit that you just publicly inherit from this class, > and add the extra stuff in, overriding any methods that you want to do > differently. (I assume the forwarders will be virtual?) I didn't think he did intend that the forwarders be virtual. If it is, then I withdraw my objection. And I am curious as to whether he has: void virtual_vector::clear() { m_vector.clear(); } or: void virtual_vector::clear() { erase( begin(), end() ); } That is, whether I have to override both erase and clear or just erase. And whether things like begin() and end() are also virtual, and whether the iterators they return have virtual methods too. It sounds like it could be a performance hit. > > In general inheriting from anything in the std library has the > > drawback that it injects unknown junk names into your class. > > Inheriting from a boost class is hardly better. > > Actually, his posted impl doesn't do that. He isn't doing, but he proposes that users do. The reason for giving boost::virtual_vector a virtual destructor is so that users can inherit from it. -- Dave Harris, Nottingham, UK.

1 0

[Boost-bugs] [ boost-Support Requests-1339778 ] Problem running configure for unsupported platform
by SourceForge.net 27 Oct '05

27 Oct '05

Support Requests item #1339778, was opened at 2005-10-27 10:59 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=1339778&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: Building Boost Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Problem running configure for unsupported platform Initial Comment: I'm trying to build Boost for HP NonStop system using a cross compiler running on cygwin. I'm just starting out trying to run ".../boost/libs/config/configure" to generate an initial confg header. This is failing on the attempt to simply compile an empty "main" configure: failed program was: | /* confdefs.h. */ | | #define PACKAGE_NAME "" | #define PACKAGE_TARNAME "" | #define PACKAGE_VERSION "" | #define PACKAGE_STRING "" | #define PACKAGE_BUGREPORT "" | /* end confdefs.h. */ | | int | main () | { | | ; | return 0; | } If I manually create such a file and compile it with the following line, I find the following: DKICK1@IL27-7496 /usr/local/boost_1_33_0/libs/config $ ls config.htm config.log configure duff.cc index.html test tools DKICK1@IL27-7496 /usr/local/boost_1_33_0/libs/config $ cat duff.cc int main () { ; return 0; } DKICK1@IL27-7496 /usr/local/boost_1_33_0/libs/config $ /usr/local/compaq-etk-nse/G06.24/bin/c89.exe -Wversion3 -Winspect -Wsaveabend -Wrefalign=2 -Wfieldalign=auto -Wnolist -Wverbose -WC -Wrunnamed -Whighpin=off -Wnld="-allow_missing_libs -libname $APPL1.CSSLIB.NLIBRARY -libvol $APPL1.CSSL IB" -Wsystype=guardian duff.cc c89 args: C:\Program Files\Compaq ETK-NSE\G06.24\bin\c89.exe -Wversion3 -Winspec t -Wsaveabend -Wrefalign=2 -Wfieldalign=auto -Wnolist -Wverbose -WC -Wrunnamed - Whighpin=off -Wnld=-allow_missing_libs -libname .CSSLIB.NLIBRARY -libvol .CSSLIB -Wsystype=guardian duff.cc C:\Program Files\Compaq ETK-NSE\G06.24\cmplr\cfe.dll loaded C:\Program Files\Compaq ETK-NSE\G06.24\cmplr\uopt.dll loaded C:\Program Files\Compaq ETK-NSE\G06.24\cmplr\ugen.dll loaded C:\Program Files\Compaq ETK-NSE\G06.24\cmplr\as1.dll loaded c89: running C:\Program Files\Compaq ETK-NSE\G06.24\cmplr\cfe.dll -ZtG -ZR2 -Zg0 -ZSD:\Profiles\DKICK1\LOCALS~1\Temp\t216328.T -ZUD:\Profiles\DKICK1\LOCALS~1\Te mp\t316328.B -D__cplusplus -a -ZnA -a -C -Zz -IC:\Program Files\Compaq ETK-NSE\G 06.24\include\ duff.cc c89: running C:\Program Files\Compaq ETK-NSE\G06.24\cmplr\ugen.dll D:\Profiles\D KICK1\LOCALS~1\Temp\t316328.B -o D:\Profiles\DKICK1\LOCALS~1\Temp\ugen216328.G - t D:\Profiles\DKICK1\LOCALS~1\Temp\t216328.T -temp D:\Profiles\DKICK1\LOCALS~1\T emp\ugen316328.t -EB -g0 -O1 -G 8 c89: running C:\Program Files\Compaq ETK-NSE\G06.24\cmplr\as1.dll D:\Profiles\DK ICK1\LOCALS~1\Temp\ugen216328.G -o duff.o -t D:\Profiles\DKICK1\LOCALS~1\Temp\t2 16328.T -Olimit 2500 -EB -g0 -O1 -elf -G 8 C:\Program Files\Compaq ETK-NSE\G06.24\cmplr\nld.dll loaded c89: running C:\Program Files\Compaq ETK-NSE\G06.24\cmplr\nld.dll -allow_missing _libs -libname .CSSLIB.NLIBRARY -libvol .CSSLIB -o a.out -elf -set systype guard ian -set highpin off -set highrequestor off -set inspect on -set runnamed on -se t saveabend on C:\Program Files\Compaq ETK-NSE\G06.24\lib\crtlmain.o C:\Program Files\Compaq ETK-NSE\G06.24\lib\cppinit3.o duff.o -L C:\Program Files\Compaq ETK -NSE\G06.24\lib\ -lstl -obey C:\Program Files\Compaq ETK-NSE\G06.24\lib\libc.obe y c89.exe: Exiting with status 0; 0 error(s). DKICK1@IL27-7496 /usr/local/boost_1_33_0/libs/config $ ls a.out config.htm config.log configure duff.cc index.html test tools DKICK1@IL27-7496 /usr/local/boost_1_33_0/libs/config $ However, if I try the following: DKICK1@IL27-7496 /usr/local/boost_1_33_0/libs/config $ sh ./configure CXX=/usr/local/compaq-etk-nse/G06.24/bin/c89 CXXFLAGS='-Wversi on3 -Winspect -Wsaveabend -Wrefalign=2 -Wfieldalign=auto -Wnolist -Wverbose -WC ' LDFLAGS='-Wrunnamed -Whighpin=off -Wnld="-allow_missing_libs -libname \ .CSSLIB.NLIBRARY -libvol $APPL1.CSSLIB" -Wsystype=guardian' I get the attached config.log. I'm sure that the problem has something to do with quoting/expansion/etc. I've tried variations on the theme, including exporting these environment variables instead of passing them on the command line, but I can't seem to find the right combination of quotes and escapes to get configure to do what I want it to do. Any help? BTW, the option to get this compiler to dump the version is '-Wversion'. $ /usr/local/compaq-etk-nse/G06.24/bin/c89.exe -Wversion @(#) $Version: T8164G09_01MAR2004_c89_05MAR2004_WIN32V_ $c89.exe: error: No input file. I'm not sure how to get configure to use this option correctly, though. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1339778&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Boost regression notification (2005-10-27 [HEAD])
by Douglas Gregor 27 Oct '05

27 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-27T05:00:12Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 340 failures in 14 libraries: concept_check (13) date_time (2) graph (2) mpl (1) parameter (2) python (1) serialization (36) spirit (8) thread (4) tr1 (133) tuple (1) type_traits (111) typeof (21) xpressive (5) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |date_time| testwcustom_time_zone: gcc-2.95.3-linux testwposix_time_zone: gcc-2.95.3-linux |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| efficiency: msvc sfinae: msvc |python| exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_array: gcc-2.95.3-linux std_test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 std_test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin std_test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_function: gcc-2.95.3-linux std_test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 std_test_hash: gcc-2.95.3-linux std_test_mem_fn: gcc-2.95.3-linux std_test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 std_test_random: gcc-2.95.3-linux std_test_reference_wrapper: gcc-2.95.3-linux std_test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_shared_ptr: gcc-2.95.3-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_array_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 test_bind: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin test_bind_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_function_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 test_functional: gcc-2.95.3-linux test_hash: gcc-2.95.3-linux test_mem_fn_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 test_memory: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_reference_wrapper_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.4.4-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple_tricky: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tr1_add_const_test: gcc-2.95.3-linux intel-win32-9_0 tr1_add_cv_test: gcc-2.95.3-linux intel-win32-9_0 tr1_add_pointer_test: gcc-2.95.3-linux intel-win32-9_0 tr1_add_reference_test: gcc-2.95.3-linux intel-win32-9_0 tr1_add_volatile_test: gcc-2.95.3-linux intel-win32-9_0 tr1_aligned_storage_test: gcc-2.95.3-linux intel-win32-9_0 tr1_alignment_of_test: gcc-2.95.3-linux intel-win32-9_0 tr1_extent_test: gcc-2.95.3-linux intel-win32-9_0 tr1_has_nothrow_assign_test: gcc-2.95.3-linux intel-win32-9_0 tr1_has_nothrow_constr_test: gcc-2.95.3-linux intel-win32-9_0 tr1_has_nothrow_copy_test: gcc-2.95.3-linux intel-win32-9_0 tr1_has_trivial_assign_test: gcc-2.95.3-linux intel-win32-9_0 tr1_has_trivial_constr_test: gcc-2.95.3-linux intel-win32-9_0 tr1_has_trivial_copy_test: gcc-2.95.3-linux intel-win32-9_0 tr1_has_trivial_destructor_test: gcc-2.95.3-linux intel-win32-9_0 tr1_has_virtual_destructor_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_abstract_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_arithmetic_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_array_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_base_of_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_class_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_compound_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_const_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_convertible_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 tr1_is_empty_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_enum_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_floating_point_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_function_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_fundamental_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_integral_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_member_func_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_member_obj_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_member_pointer_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_object_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_pod_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_pointer_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_polymorphic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux intel-win32-9_0 tr1_is_reference_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_same_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_scalar_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_signed_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_union_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_unsigned_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_void_test: gcc-2.95.3-linux intel-win32-9_0 tr1_is_volatile_test: gcc-2.95.3-linux intel-win32-9_0 tr1_rank_test: gcc-2.95.3-linux intel-win32-9_0 tr1_remove_all_extents_test: gcc-2.95.3-linux intel-win32-9_0 tr1_remove_const_test: gcc-2.95.3-linux intel-win32-9_0 tr1_remove_cv_test: gcc-2.95.3-linux intel-win32-9_0 tr1_remove_extent_test: gcc-2.95.3-linux intel-win32-9_0 tr1_remove_pointer_test: gcc-2.95.3-linux intel-win32-9_0 tr1_remove_reference_test: gcc-2.95.3-linux intel-win32-9_0 tr1_remove_volatile_test: gcc-2.95.3-linux intel-win32-9_0 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

Bug list status
by Marshall Clow 27 Oct '05

27 Oct '05

Three weeks ago: 144 open bugs Two weeks ago: 117 open bugs Last week: 96 open bugs Today: 94 open bugs Thanks to everyone who dealt with the bugs! [ But we're slowing down - I blame the 1.33.1 release process ;-) ] Here are the currently opened bugs, sorted by assignee. If you think that a bug has been assigned incorrectly, please let me know. P.S. I need someone to fix the bugs in the tokenizer library!! Assignee: agurtovoy <http://sourceforge.net/users/agurtovoy/> Summary: mpl::select2nd on vc6 Bug #: 812263 <http://sourceforge.net/tracker/index.php?func=detail&aid=812263&group_id=75…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: wrong usage of ios_base::narrow Bug #: 989487 <http://sourceforge.net/tracker/index.php?func=detail&aid=989487&group_id=75…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: date_time type conversion warning Bug #: 1069225 <http://sourceforge.net/tracker/index.php?func=detail&aid=1069225&group_id=7…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: local_adjustor::utc_to_local throws 'Time label invalid' Bug #: 1220011 <http://sourceforge.net/tracker/index.php?func=detail&aid=1220011&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: filesytem::directory_iterator portability Bug #: 735403 <http://sourceforge.net/tracker/index.php?func=detail&aid=735403&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem fails in posix with files containing ':' Bug #: 776146 <http://sourceforge.net/tracker/index.php?func=detail&aid=776146&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: clock is not portable Bug #: 788762 <http://sourceforge.net/tracker/index.php?func=detail&aid=788762&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: Boost::Filesystem fails when last character in path is ':' Bug #: 875970 <http://sourceforge.net/tracker/index.php?func=detail&aid=875970&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: filesystem::directory_iterator returns incorrect listing Bug #: 937606 <http://sourceforge.net/tracker/index.php?func=detail&aid=937606&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: xtime_cmp: use comparison not subtraction Bug #: 993272 <http://sourceforge.net/tracker/index.php?func=detail&aid=993272&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::exists is broken on cygwin Bug #: 1010681 <http://sourceforge.net/tracker/index.php?func=detail&aid=1010681&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem is systematically broken Bug #: 1012135 <http://sourceforge.net/tracker/index.php?func=detail&aid=1012135&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::native() should reject '/' on non-Win32 Bug #: 1151823 <http://sourceforge.net/tracker/index.php?func=detail&aid=1151823&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::exists has bugs with UNC paths Bug #: 1164057 <http://sourceforge.net/tracker/index.php?func=detail&aid=1164057&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::equivalent does not work on w98 Bug #: 1235262 <http://sourceforge.net/tracker/index.php?func=detail&aid=1235262&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: path and directory_iterator doesn't handle windows root path Bug #: 1259176 <http://sourceforge.net/tracker/index.php?func=detail&aid=1259176&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: no conversion from type to const_type Bug #: 547743 <http://sourceforge.net/tracker/index.php?func=detail&aid=547743&group_id=75…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: EdgeListS = setS for adjacency_list does not work Bug #: 1163077 <http://sourceforge.net/tracker/index.php?func=detail&aid=1163077&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: adjacency_matrix should model BidirectionalGraph Bug #: 1168411 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168411&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA graph adaptors for undirected graphs Bug #: 1168420 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168420&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA adaptors for node_array, edge_array Bug #: 1168424 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168424&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA graph adaptors do not handle hidden nodes properly Bug #: 1168431 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168431&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Generate patches for Graph bugs in 1.32.0 Bug #: 1169920 <http://sourceforge.net/tracker/index.php?func=detail&aid=1169920&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Investigate other kinds of heaps for dijkstra_shortest_paths Bug #: 1170106 <http://sourceforge.net/tracker/index.php?func=detail&aid=1170106&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: function.hpp breaks assign.hpp Bug #: 1181272 <http://sourceforge.net/tracker/index.php?func=detail&aid=1181272&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: vertex bundle properties do not work with VC++.NET 2003 Bug #: 1190394 <http://sourceforge.net/tracker/index.php?func=detail&aid=1190394&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: BGL graph types do not support allocators Bug #: 1193883 <http://sourceforge.net/tracker/index.php?func=detail&aid=1193883&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: random_vertex/random_edge are unnecessarily inefficient Bug #: 1204684 <http://sourceforge.net/tracker/index.php?func=detail&aid=1204684&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Document copy_component Bug #: 1204688 <http://sourceforge.net/tracker/index.php?func=detail&aid=1204688&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: reverse_graph and constness of property maps Bug #: 1246336 <http://sourceforge.net/tracker/index.php?func=detail&aid=1246336&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: html docs frequently missing key words Bug #: 1294420 <http://sourceforge.net/tracker/index.php?func=detail&aid=1294420&group_id=7…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: Miss ' = ParserT()' Bug #: 907299 <http://sourceforge.net/tracker/index.php?func=detail&aid=907299&group_id=75…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: spirit insert_key_actor.hpp Bug #: 1059936 <http://sourceforge.net/tracker/index.php?func=detail&aid=1059936&group_id=7…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: Another config correction for Sun C++ Bug #: 1220782 <http://sourceforge.net/tracker/index.php?func=detail&aid=1220782&group_id=7…> Assignee: dlwalker <http://sourceforge.net/users/dlwalker/> Summary: template problems with common_factor.hpp Bug #: 491637 <http://sourceforge.net/tracker/index.php?func=detail&aid=491637&group_id=75…> Assignee: ebf <http://sourceforge.net/users/ebf/> Summary: boost::blank - missing operators Bug #: 1191356 <http://sourceforge.net/tracker/index.php?func=detail&aid=1191356&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: timeconv.inl to_duration() nsec error Bug #: 548104 <http://sourceforge.net/tracker/index.php?func=detail&aid=548104&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Solaris - once.cpp compile error Bug #: 549162 <http://sourceforge.net/tracker/index.php?func=detail&aid=549162&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: pthread_delay_np() parm incorrect Bug #: 551157 <http://sourceforge.net/tracker/index.php?func=detail&aid=551157&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Bosot.Thread.condition(win32).notify_all Bug #: 551308 <http://sourceforge.net/tracker/index.php?func=detail&aid=551308&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: AIX 4.3 SIGSEGV at thread termination Bug #: 551577 <http://sourceforge.net/tracker/index.php?func=detail&aid=551577&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: boost::threads uses msvc only function? Bug #: 568951 <http://sourceforge.net/tracker/index.php?func=detail&aid=568951&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: threads unnecessary #include Bug #: 571615 <http://sourceforge.net/tracker/index.php?func=detail&aid=571615&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: BCB6 throw EExternelException Bug #: 596149 <http://sourceforge.net/tracker/index.php?func=detail&aid=596149&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: thread_cleanup problems Bug #: 649291 <http://sourceforge.net/tracker/index.php?func=detail&aid=649291&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Mac implementation of threads is CPU hog Bug #: 885045 <http://sourceforge.net/tracker/index.php?func=detail&aid=885045&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: condition variables and recursive_mutex Bug #: 1072605 <http://sourceforge.net/tracker/index.php?func=detail&aid=1072605&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: compiler error on Mac implementation of threads Bug #: 1201779 <http://sourceforge.net/tracker/index.php?func=detail&aid=1201779&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: timeconv.inl line 116 copy/paste error Bug #: 1239052 <http://sourceforge.net/tracker/index.php?func=detail&aid=1239052&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Exception safety in class 'thread' Bug #: 1305885 <http://sourceforge.net/tracker/index.php?func=detail&aid=1305885&group_id=7…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: 'failed fileclone' when building with -j on 1.32.0 Bug #: 1102389 <http://sourceforge.net/tracker/index.php?func=detail&aid=1102389&group_id=7…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: boost jam problem with parallel builds Bug #: 1234224 <http://sourceforge.net/tracker/index.php?func=detail&aid=1234224&group_id=7…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer fails with wchar_t Bug #: 446155 <http://sourceforge.net/tracker/index.php?func=detail&aid=446155&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer not works with Dinkumware 308 Bug #: 458236 <http://sourceforge.net/tracker/index.php?func=detail&aid=458236&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: boost::tokenizer implicit typename Bug #: 912368 <http://sourceforge.net/tracker/index.php?func=detail&aid=912368&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: Tokenizer.hpp doesn't work with BOOST_ENABLE_ASSERT_HANDLER Bug #: 972406 <http://sourceforge.net/tracker/index.php?func=detail&aid=972406&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: Compiler error for tokenizer on Solaris Bug #: 976241 <http://sourceforge.net/tracker/index.php?func=detail&aid=976241&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer and signed char Bug #: 1003889 <http://sourceforge.net/tracker/index.php?func=detail&aid=1003889&group_id=7…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: token_iterator::at_end() result is inversed Bug #: 1338326 <http://sourceforge.net/tracker/index.php?func=detail&aid=1338326&group_id=7…> Assignee: jmaurer <http://sourceforge.net/users/jmaurer/> Summary: Diff in state of mersenne_twister gen between GCC3.41 & CW9 Bug #: 1115124 <http://sourceforge.net/tracker/index.php?func=detail&aid=1115124&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: bug in ublas/storage.hpp Bug #: 1095697 <http://sourceforge.net/tracker/index.php?func=detail&aid=1095697&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: dead links in uBLAS page Bug #: 1169273 <http://sourceforge.net/tracker/index.php?func=detail&aid=1169273&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: Documentation not available on web site: Bug #: 1228242 <http://sourceforge.net/tracker/index.php?func=detail&aid=1228242&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: uBLAS::subslice doesn't work Bug #: 1292635 <http://sourceforge.net/tracker/index.php?func=detail&aid=1292635&group_id=7…> Assignee: johnmaddock <http://sourceforge.net/users/johnmaddock/> Summary: Adding boost::is_complex to type_traits.hpp Bug #: 1315712 <http://sourceforge.net/tracker/index.php?func=detail&aid=1315712&group_id=7…> Assignee: jsiek <http://sourceforge.net/users/jsiek/> Summary: invalid result for File Dependency Examp Bug #: 551110 <http://sourceforge.net/tracker/index.php?func=detail&aid=551110&group_id=75…> Assignee: jsiek <http://sourceforge.net/users/jsiek/> Summary: Spelling of Edmonds-Karp-Algorithm Bug #: 1226292 <http://sourceforge.net/tracker/index.php?func=detail&aid=1226292&group_id=7…> Assignee: mark_rodgers <http://sourceforge.net/users/mark_rodgers/> Summary: Cannot compile octonion_test.cpp because of bug in sinc.hpp Bug #: 751269 <http://sourceforge.net/tracker/index.php?func=detail&aid=751269&group_id=75…> Assignee: mark_rodgers <http://sourceforge.net/users/mark_rodgers/> Summary: Cannot compile octonion_test.cpp because of bug in sinc.hpp Bug #: 751289 <http://sourceforge.net/tracker/index.php?func=detail&aid=751289&group_id=75…> Assignee: nesotto <http://sourceforge.net/users/nesotto/> Summary: boost.range and 'const char[]'. Bug #: 1272315 <http://sourceforge.net/tracker/index.php?func=detail&aid=1272315&group_id=7…> Assignee: nobody Summary: failure in boost jam unit tests on cygwin Bug #: 940941 <http://sourceforge.net/tracker/index.php?func=detail&aid=940941&group_id=75…> Assignee: nobody Summary: Can't build on cygwin Bug #: 1145183 <http://sourceforge.net/tracker/index.php?func=detail&aid=1145183&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: many 'virtual functions vs. non-virtual destructor' warnings Bug #: 1312222 <http://sourceforge.net/tracker/index.php?func=detail&aid=1312222&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: Compiler warning with gcc on Linux Bug #: 1337412 <http://sourceforge.net/tracker/index.php?func=detail&aid=1337412&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: warning caused by size_t to unsigned int conversion on vc++8 Bug #: 1338178 <http://sourceforge.net/tracker/index.php?func=detail&aid=1338178&group_id=7…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: typo in Boost.Test document Bug #: 629685 <http://sourceforge.net/tracker/index.php?func=detail&aid=629685&group_id=75…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: BOOST_CHECK_CLOSE in Boost Test Library Bug #: 754551 <http://sourceforge.net/tracker/index.php?func=detail&aid=754551&group_id=75…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: BOOST_AUTO_TEST doesn't work across multiple units Bug #: 823589 <http://sourceforge.net/tracker/index.php?func=detail&aid=823589&group_id=75…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: Bug in build via MSVC Solution Bug #: 953876 <http://sourceforge.net/tracker/index.php?func=detail&aid=953876&group_id=75…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: Don't work multilevel hierarchy of test suites in dll. Bug #: 1076691 <http://sourceforge.net/tracker/index.php?func=detail&aid=1076691&group_id=7…> Assignee: samuel_k <http://sourceforge.net/users/samuel_k/> Summary: format: assert when parsing invalid pattern Bug #: 1326132 <http://sourceforge.net/tracker/index.php?func=detail&aid=1326132&group_id=7…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: ct_gcd_lcm.hpp compilation error Bug #: 558174 <http://sourceforge.net/tracker/index.php?func=detail&aid=558174&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: test_pool_alloc.cpp not compile CW8.1 Bug #: 586779 <http://sourceforge.net/tracker/index.php?func=detail&aid=586779&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: pool::purge_memory() does not reset next_size Bug #: 984124 <http://sourceforge.net/tracker/index.php?func=detail&aid=984124&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: Borland compiler error with Pool, boost::pool_allocator Bug #: 988124 <http://sourceforge.net/tracker/index.php?func=detail&aid=988124&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: perfomance: memory cleanup for pool takes too long Bug #: 995270 <http://sourceforge.net/tracker/index.php?func=detail&aid=995270&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: boost::pool_allocator breaks with vector of vectors Bug #: 1179641 <http://sourceforge.net/tracker/index.php?func=detail&aid=1179641&group_id=7…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: Self division wrong in template rational Bug #: 504411 <http://sourceforge.net/tracker/index.php?func=detail&aid=504411&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: Rational sum not optimal for overflows Bug #: 519635 <http://sourceforge.net/tracker/index.php?func=detail&aid=519635&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: rational operator&lt; can overflow Bug #: 798357 <http://sourceforge.net/tracker/index.php?func=detail&aid=798357&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: boost::rational documentation typos(?) Bug #: 1043616 <http://sourceforge.net/tracker/index.php?func=detail&aid=1043616&group_id=7…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: no Boolean conversion for boost::rational Bug #: 1239906 <http://sourceforge.net/tracker/index.php?func=detail&aid=1239906&group_id=7…> Assignee: vladimir_prus <http://sourceforge.net/users/vladimir_prus/> Summary: call to split_winmain raises exception for 8-bit locale Bug #: 1206663 <http://sourceforge.net/tracker/index.php?func=detail&aid=1206663&group_id=7…> Assignee: vladimir_prus <http://sourceforge.net/users/vladimir_prus/> Summary: multitoken broken in program_options 1.33 Bug #: 1266877 <http://sourceforge.net/tracker/index.php?func=detail&aid=1266877&group_id=7…> -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

3 2

Interest in dimension/unit-checking library?
by Geoffrey Romer 27 Oct '05

27 Oct '05

Would there be any interest in a library for attaching units (physical or otherwise) to numeric variables, so that the type system could enforce dimension- and unit-consistency in all calculations, and convert semi-automatically between compatible units? To make this a little more concrete, here's a sketch of the kind of code such a library could enable: --- quantity<meters, double> distance(1.0); quantity<newtons, double> force(5.0); quantity<joules, double> work = distance * force; quantity<calories, double> work_cal = unit_cast<calories>(work); work_cal = work; //Compile error or implicit conversion, // possibly depending on compiler flag quantity<watts, double> power = work; //Compile error- incompatible types --- This library would be somewhat similar to the dimensional-analysis code given by Abrahams and Gurtovoy in their book[1], but with two major enhancements: - it would be defined in terms of specific units (as Abrahams and Gurtovoy suggest in an exercise), rather than general dimensions, so it could catch unit-consistency errors as well as dimension-consistency errors, and it could convert between compatible units - it would allow client code to extend the system with arbitrary units in arbitrary dimensions I should note that although I gave the example in terms of physical units for clarity, I intend this library to be useful not just for physical calculation, but for numerical calculation in general. Almost any time software deals with numbers, it's really dealing with *quantities* (numbers that measure something in terms of some unit), and errors can result if variables with different units are inappropriately combined. The purpose of this library would be to allow developers to prevent those errors with strong typing and compile-time checking, as well as to somewhat ease the task of converting between units when necessary. I know there's been a lot of discussion of units for a GUI library, so I'm especially interested in what people involved in that thread think of this idea- I want to make something sufficiently powerful to be useful in a context like that. [1] http://www.boost.org/libs/mpl/doc/tutorial/tutorial-metafunctions.html

18 100

[range][1.33.1] last few regressions.
by John Maddock 27 Oct '05

27 Oct '05

Otto, can the last few regressions for the range lib be fixed (http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i…) or should these just be marked up as expected? Thanks, John.

7 9

Re: [boost] Is there any interest in a library that provides container
by brangdon＠cix.compulink.co.uk 27 Oct '05

27 Oct '05

In-Reply-To: <1130256273.28161.245978560(a)webmail.messagingengine.com> atompkins(a)fastmail.fm (Andy Tompkins) wrote (abridged): > I have read a few times that people sometimes wish that std::vector (or > other containers) had a virtual destructor. Generally when I've wished for that I've also wished for a few other virtual functions. For example, a hook which gets called whenever an item is added to the vector, and another which is called when items are removed. I think a vector which is designed to be derived from would need more than just a virtual destructor. If you are adding a vtable you might as well get some milage out of it. On the other hand, I rarely need my container to be polymorphic - at least, not with respect to some library base class like std::vector or boost::virtual_vector. Nor do I usually want my container to have the entire interface of vector. For example, I may not want to allow arbitrary insertion at all. So I tend to write a custom wrapper class that has vector as a private member and just exposes what I need. In general inheriting from anything in the std library has the drawback that it injects unknown junk names into your class. Inheriting from a boost class is hardly better. So overall, I'm not in favour. -- Dave Harris, Nottingham, UK.

3 2

[MPL.Math] gcd_impl improved
by Cromwell Enage 27 Oct '05

27 Oct '05

The gcd_impl specialization for integral constants is now based on the binary GCD algorithm. BOOST_STATIC_CONSTANT is now used over typedef at most intermediate steps. You should see much faster compile times, at least for the gcd_lcm test and example programs. Cromwell D. Enage __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com

1 0

[MPL.Math] numeric_downcast or round_up?
by Cromwell Enage 27 Oct '05

27 Oct '05

--- Simon Buchan wrote: > David Abrahams wrote: > > my_rational<x,1> can be an integral constant *at > > compile time*. I'm not sure it's useful, but > > it's not insane. > > If you for some reason still think this, why not > eagerly evaluate > template<typename Num> > rational<Num,1> > to Num, since we are already eagerly normalising? It's possible to do so, but I see three concerns. One, we need to be careful where to do it. Putting this capability directly in the definition of rational makes expressions like rational<int_<4> > rather useless. Employing downcasting on the result of each rational operation leads us to the second concern: performance. Computationally heavy numeric metafunctions (e.g. exponential, sine) are going to pay extra at each step checking for an event that may never occur. And even if downcasting occurs half the time, if there are just as many regular casts back to rational, we end up overpaying twice as much. We could give users the ability to explicitly downcast any numeric constant. This leads us to the final concern: usefulness. For the moment, I don't see any need beyond rounding; the library provides a numeric metafunction called whole_part if you want truncation. If anybody needs either downcasting or rounding, we'd like to hear from you. Cromwell D. Enage __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

[MPL.Math] divergent results for double.cpp
by Cromwell Enage 27 Oct '05

27 Oct '05

Running the example program with MSVC7.1 works as expected. With MinGW I'm forced to use string_c_to_double rather than BOOST_MPL_MATH_DOUBLE. However, it looks like some less-significant bits are getting lost in the translation, as the corresponding log shows. Something may be up with string_c_to_double_impl. Cromwell D. Enage __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

2 4

[program_options] allowing unknown options (from third party libraries)
by Christophe Prud'homme 27 Oct '05

27 Oct '05

Dear Boosters, I could not find in the doc whether it is possible to have unknown options in the command line and tell the parsers to not worry about them. If it is already a feature, then perhaps it should be documented. Otherwise I think it could be a nice addition. the rationale is that there are framework/libraries out there with there own command line options : for example MPI and PETSC Best regards C. -- MIT Affiliate Debian/GNU/Linux developer for scientific computing packages fingerprint = 3703 50DE 7A9F 024E 0F26 0D07 A18F B40B D4BE 1450

2 3

[parameter][1.33.1] last few failures
by John Maddock 27 Oct '05

27 Oct '05

Dave, Daniel, are the last few failures (http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i…) of the parameter lib fixable or should they be marked up? Thanks, John.

3 8

Re: [boost] Is there any interest in a library that provides cont ainers with virtual destructors?
by Martin Bonner 27 Oct '05

27 Oct '05

----Original Message---- From: Victor A. Wagner Jr. [mailto:vawjr@rudbek.com] Sent: 27 October 2005 03:55 To: boost(a)lists.boost.org; boost(a)lists.boost.org Subject: Re: [boost] Is there any interest in a library that provides containers with virtual destructors? > [deleted] > >>>> >>>> are you suggesting that if it were class people: public >>>> std::vector<person> {.....}; as above the same would be true? >>>> not "in practice", "in theory". >>> >>> Absolutely. See 5.3.5/1 of the standard where this is explicitly >>> called out as undefined behaviour. > > 5.3.5/1 looks like this in my copy of the standard [snip] > > perhaps some other paragraph? this doesn't address anything about > derived objects. D'oh! As others have pointed out, I meant 5.3.5/3. Sorry about that :-( -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

1 0

range idea (single)
by Neal Becker 27 Oct '05

27 Oct '05

Suppose one adopts the range concept. All algorithms are written to accept ranges as arguments. It is common to want to implement a function F, which operates on one data element. For example: template<typename T> T sqr (T x) { return x * x; } Also, implement a version that operates on a container. This could be done by defining only the single element version, and a version of transform, that operates on ranges. Here's an interesting idea. Suppose instead that only the range version of F is defined, but a range type is made that encapsulates a single element. Again, only 1 version of F needs to be defined. Here is an outline: template<typename T> struct Single { typedef T* iterator; typedef const T* const_iterator; typedef size_t size_type; Single (T& _x) : x (_x) {} T& x; size_t size() const { return 1; } iterator begin() { return &x; } const_iterator begin() const { return &x; } iterator end() { return &x+1; } const_iterator end() const { return &x+1; } // not complete yet... }; // Test program... template<typename out_t, typename in_t> out_t copy (in_t const& in) { out_t out (boost::size (in)); std::copy (boost::begin (in), boost::end (in), boost::begin (out)); return out; } int main() { using namespace std; using namespace boost; int x; Single<int> s (x); vector<int> v = copy<vector<int> > (s); }

3 2

Re: [boost] Is there any interest in a library that provides containers with virtual destructors?
by Victor A. Wagner Jr. 27 Oct '05

27 Oct '05

At 21:52 2005-10-26, Matt Calabrese wrote: >On 10/26/05, Victor A. Wagner Jr. <vawjr(a)rudbek.com> wrote: > > > perhaps some other paragraph? this doesn't address anything about > > derived objects. > > >Just look 2 paragraphs further: > >5.3.5 paragraph 3 > >"In the first alternative (delete object), if the static type of the operand >is different from its dynamic type, the static type shall be a base class of >the operand's dynamic type and the static type shall have a virtual >destructor or the behavior is undefined." ... indeed, but there is no dynamic type vs static type in the example. >The paragraph then goes further to talk about arrays. > >As for interest in the STL containers with virtual destructors, I'd >personally say no. I didn't suggest them, I'm arguing that for the example given they aren't necessary > I've never encountered a situation where it would be >useful or at least useful and better than other alternatives. Anyway, the >desire for a virtual destructor could exist with any type. If someone wants >virtual destructors for STL containers, then what next? multi_array with >virtual destructors? graphs? Forgive me if that sounds like a slippery slope >argument, but really I see no logic as to why one would want virtual >destructors for STL containers yet not any other types. You can use the same >type of argument for any type you can think of -- "I want to derive from the >type and then add functionality, but want to delete it via a pointer to the >base class". I have never said such. I don't know where you got the idea I had. > Does this mean that all types should have one version with >virtual destructors, and one without? Definately not. I just don't see why >someone would want to make the exception for STL containers. > >-- >-Matt Calabrese >_______________________________________________ >Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

2 1

[iterator] huge differences in compile time between iterator_facade and iterator helpers
by Joaquín Mª López Muñoz 26 Oct '05

26 Oct '05

While in the process of replacing iterator helpers from <boost/operators.hpp> in favor of boost::iterator_facade as my internal iterator generation lib in Boost.MultiIndex, I've discovered an unpleasant increase in compilation times. The attached program shows the problem. Compilation times when using boost::iterator_facade are *way* higher than with good old boost::bidirectional_iterator_helper (to test it yourself, just comment/uncomment the line "#define USE_BOOST_ITERATOR" in the program): MSVC++ 6.0: iterator_facade: ~7 sec. bidirectional_iterator_helper: less than 1 sec. GCC 3.2 iterator_facade: 4.9 sec. bidirectional_iterator_helper: 2.5 sec. My questions: 1. Maybe the test program is flawed and has some (unseen by me) bias in favor of bidirectional_iterator_helper? 2. If not so, why is iterator_facade so very expensive? Is there any way to alleviate the problem? As it stands, I'm not so sure it's a good idea to adopt boost::iterator_facade: my local tests for Boost.MultiIndex show an overall increase in compilation time of around 25% :( Thanks for your help, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 8

Re: [boost] FW: [Xpressive] quantify embedded regex - still no joy
by BRIDGES Dick 26 Oct '05

26 Oct '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of Eric Niebler > Sent: Tuesday, October 25, 2005 10:59 AM > To: boost(a)lists.boost.org > Subject: Re: [boost] FW: [Xpressive] quantify embedded regex > - still no joy > > BRIDGES Dick wrote: > > I ran the softfloat ARM cross-comiler against the exemplar and it > > compiled. Problem seems to be the x86 gcc 3.4.2 compiler? > > It appears so. According to the regression tests, quantifying an > embedded regex compiles on gcc-3.4.4-linux (see misc1 test at > http://tinyurl.com/dyaub) I guess gcc-3.4.2 is broken wrt > xpressive. Sorry. > > -- > Eric Niebler > Boost Consulting > www.boost-consulting.com No problem. Updated to gcc-3.4.4 and it compiles just dandy. I never did like that old compiler anyway. ;) Thank you very much for your help. Regards, Dick Bridges

2 1

[1.33.1] spurious Borland failures in serialisation lib?
by John Maddock 26 Oct '05

26 Oct '05

The remaining Borland failures for the serialisation lib in 1.33.1 appear to be spurious, or at least the HTML is all mixed up, the links all lead to digital-mars failures! Any ideas what's happening? Thanks, John.

1 0

Boost regression notification (2005-10-26 [HEAD])
by Douglas Gregor 26 Oct '05

26 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-26T05:00:18Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 430 failures in 14 libraries: concept_check (13) date_time (2) graph (2) mpl (1) parameter (2) python (1) serialization (40) spirit (8) thread (4) tr1 (12) tuple (1) type_traits (318) typeof (21) xpressive (5) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |date_time| testwcustom_time_zone: gcc-2.95.3-linux testwposix_time_zone: gcc-2.95.3-linux |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| efficiency: msvc sfinae: msvc |python| exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc test_tracking_binary_archive: vc-7_1 test_tracking_text_warchive: vc-7_1 test_tracking_xml_archive: vc-7_1 test_variant_text_warchive_dll: vc-7_1 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tr1| std_test_array_tricky: vc-7_1 std_test_bind_tricky: vc-7_1 std_test_function_tricky: vc-7_1 std_test_mem_fn_tricky: vc-7_1 std_test_reference_wrapper_tricky: vc-7_1 std_test_tuple_tricky: vc-7_1 test_array_tricky: vc-7_1 test_bind_tricky: vc-7_1 test_function_tricky: vc-7_1 test_mem_fn_tricky: vc-7_1 test_reference_wrapper_tricky: vc-7_1 test_tuple_tricky: vc-7_1 |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tr1_add_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_add_cv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_add_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_add_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_add_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_aligned_storage_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_alignment_of_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_extent_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_has_nothrow_assign_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_has_nothrow_constr_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_has_nothrow_copy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_has_trivial_assign_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_has_trivial_constr_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_has_trivial_copy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_has_trivial_destructor_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_has_virtual_destructor_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_abstract_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_arithmetic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_array_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_base_of_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_class_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_compound_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_convertible_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_empty_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_enum_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_floating_point_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_function_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_fundamental_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_integral_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_member_func_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_member_obj_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_member_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_object_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_pod_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_polymorphic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_same_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_scalar_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_signed_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_union_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_unsigned_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_void_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_is_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_rank_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_remove_all_extents_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_remove_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_remove_cv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_remove_extent_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_remove_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_remove_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_remove_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5u: gcc-3_3-darwin test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

Re: [boost] Is there any interest in a library that provides cont ainers with virtual destructors?
by Victor A. Wagner Jr. 26 Oct '05

26 Oct '05

At 02:51 2005-10-26, Martin Bonner wrote: >----Original Message---- >From: Victor A. Wagner Jr. [mailto:vawjr@rudbek.com] >Sent: 26 October 2005 05:36 >To: boost(a)lists.boost.org; boost(a)lists.boost.org >Subject: Re: [boost] Is there any interest in a library that provides >containers with virtual destructors? > > > At 10:04 2005-10-25, Andy Tompkins wrote: > >> I have read a few times that people sometimes wish that std::vector > >> (or other containers) had a virtual destructor. >[snip] > >> This allows one to write something like: > >> > >> struct person { > >> string first_name; > >> string last_name; > >> }; > >> class people : public virtual_vector<person> > >> { > >> public: > >> //extra methods > >> }; > >> > >> Is this useful? > > > > unless I mis-read (or mis-understood...far more likely) a lot of > > books on how C++ works, I don't believe there is any reason for what > > _you've_ shown to need a virtual destructor. > >You have mis-read or mis-understood (or you need better books). Consider: > virtual_vector<person>* p = new people; I guees I wasn't clear.. I was suggesting that virtual_vector has no need for existence. > delete p; >That invokes undefined behaviour unless virtual_vector<person> has a virtual >destructor. are you suggesting that if it were class people: public std::vector<person> {.....}; as above the same would be true? not "in practice", "in theory". >In *practise*, you will (probably) get away with it. The most *likely* >behaviour is that virtual_vector<>::~virtual_vector() will be called, >without calling people::~people(). ... but that doesn't alter the fact that >it *is* undefined behaviour, which is not good. > > > >-- >Martin Bonner >Martin.Bonner(a)Pitechnology.com >Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, >ENGLAND Tel: +44 (0)1223 441434 >_______________________________________________ >Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

1 0

[Boost-bugs] [ boost-Bugs-1338326 ] token_iterator::at_end() result is inversed
by SourceForge.net 26 Oct '05

26 Oct '05

Bugs item #1338326, was opened at 2005-10-26 03:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1338326&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: token_iterator::at_end() result is inversed Initial Comment: token_iterator::at_end() returns true when our iterator is not at end and false othervise. It should return !valid_. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1338326&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] Is there any interest in a library that provides cont ainers with virtual destructors?
by Martin Bonner 26 Oct '05

26 Oct '05

----Original Message---- From: Victor A. Wagner Jr. [mailto:vawjr@rudbek.com] Sent: 26 October 2005 05:36 To: boost(a)lists.boost.org; boost(a)lists.boost.org Subject: Re: [boost] Is there any interest in a library that provides containers with virtual destructors? > At 10:04 2005-10-25, Andy Tompkins wrote: >> I have read a few times that people sometimes wish that std::vector >> (or other containers) had a virtual destructor. [snip] >> This allows one to write something like: >> >> struct person { >> string first_name; >> string last_name; >> }; >> class people : public virtual_vector<person> >> { >> public: >> //extra methods >> }; >> >> Is this useful? > > unless I mis-read (or mis-understood...far more likely) a lot of > books on how C++ works, I don't believe there is any reason for what > _you've_ shown to need a virtual destructor. You have mis-read or mis-understood (or you need better books). Consider: virtual_vector<person>* p = new people; delete p; That invokes undefined behaviour unless virtual_vector<person> has a virtual destructor. In *practise*, you will (probably) get away with it. The most *likely* behaviour is that virtual_vector<>::~virtual_vector() will be called, without calling people::~people(). ... but that doesn't alter the fact that it *is* undefined behaviour, which is not good. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

1 0

[Boost-bugs] [ boost-Bugs-1338178 ] warning caused by size_t to unsigned int conversion on vc++8
by SourceForge.net 26 Oct '05

26 Oct '05

Bugs item #1338178, was opened at 2005-10-26 01:10 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1338178&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: serialization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Robert Ramey (ramey) Summary: warning caused by size_t to unsigned int conversion on vc++8 Initial Comment: This is in collections_save_imp.hpp, line 36: unsigned int count = s.size(); I get a warning under vc++8: c:\boost\include\boost-1_33\boost\serialization\collections_save_imp.hpp(36) : warning C4267: 'initializing' : conversion from 'size_t' to 'unsigned int', possible loss of data I don't know if this is a foolish warning or not, or if changing to size_t would be detrimental to other platforms, but I thought I'd point it out just in case. bhiggins(a)gmail.com ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1338178&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Is there any interest in a library that provides containers with virtual destructors?
by Andy Tompkins 26 Oct '05

26 Oct '05

I have read a few times that people sometimes wish that std::vector (or other containers) had a virtual destructor. I have recently wished for the same thing and I fairly quickly write a class called virtual_vector something like: template <class Type, class Allo = std::allocator<Type> > class virtual_vector { public: ~virtual_vector(); ... private: std::vector<Type, Alloc> m_vector; }; All the public methods of std::vector are present in virtual_vector and are just forwarded on m_vector. This allows one to write something like: struct person { string first_name; string last_name; }; class people : public virtual_vector<person> { public: //extra methods }; Is this useful? Has this been done already? Thanks in advance for any comments? Andy Tompkins

2 1

Boost regression notification (2005-10-25 [RC_1_33_0])
by Douglas Gregor 25 Oct '05

25 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-25T14:49:08Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 58 failures in 3 libraries: parameter (2) range (3) serialization (53) |parameter| tutorial: borland-5_6_4 gcc-2.95.3-linux |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_class_info_load_binary_archive: cw-9_4 cw-9_5-darwin gcc-3_4_3-sunos mingw-3_4_2 test_class_info_load_binary_archive_dll: cw-9_4 cw-9_5-darwin gcc-3_4_3-sunos intel-win32-8_1 mingw-3_4_2 test_class_info_load_text_archive: cw-9_4 gcc-3_4_3-sunos mingw-3_4_2 test_class_info_load_text_archive_dll: cw-9_4 gcc-3_4_3-sunos intel-win32-8_1 mingw-3_4_2 test_class_info_load_text_warchive: cw-9_4 gcc-3_4_3-sunos test_class_info_load_text_warchive_dll: cw-9_4 gcc-3_4_3-sunos intel-win32-8_1 test_class_info_load_xml_archive: cw-9_4 cw-9_5-darwin gcc-3_4_3-sunos mingw-3_4_2 test_class_info_load_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3_4_3-sunos intel-win32-8_1 mingw-3_4_2 test_class_info_load_xml_warchive: cw-9_4 gcc-3_4_3-sunos test_class_info_load_xml_warchive_dll: cw-9_4 gcc-3_4_3-sunos intel-win32-8_1 test_demo_xml_load: gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 mingw-3_4_2 test_demo_xml_load_dll: gcc-3_4_3-sunos gcc-4_0-darwin mingw-3_4_2 test_shared_ptr_132_text_warchive: intel-win32-8_1 test_shared_ptr_binary_archive: borland-5_6_4 test_shared_ptr_binary_archive_dll: borland-5_6_4 test_shared_ptr_text_archive: borland-5_6_4 test_shared_ptr_text_archive_dll: borland-5_6_4 test_shared_ptr_text_warchive: borland-5_6_4 test_shared_ptr_text_warchive_dll: borland-5_6_4 test_shared_ptr_xml_archive: borland-5_6_4 test_shared_ptr_xml_archive_dll: borland-5_6_4 test_shared_ptr_xml_warchive: borland-5_6_4 test_shared_ptr_xml_warchive_dll: borland-5_6_4

4 5

[Boost-bugs] [ boost-Support Requests-1337851 ] unknown compiler version
by SourceForge.net 25 Oct '05

25 Oct '05

Support Requests item #1337851, was opened at 2005-10-25 16:53 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=1337851&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: Building Boost Group: None Status: Open Resolution: None Priority: 5 Submitted By: dstjames (dstjames) Assigned to: Nobody/Anonymous (nobody) Summary: unknown compiler version Initial Comment: I am not a developer but I need the boost librarys to compile a program I want to look at. When I try to install the boost library for GCC version 4.0.2_20050901-3 on SUSE 10.0 I get into an infinate loop where it keeps telling me unknown compiler version over and over. I am using the command bjam "-sTOOLS=gcc" install. Anyone know what this error means or a workaround? Thanks for any help. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1337851&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

boost::bind trouble
by Neal Becker 25 Oct '05

25 Oct '05

I'm using bind with boost-1.33. I can't get a simple test to work: ----------- #include <boost/bind.hpp> int G (int a, int b, int c) { return a + b + c; } int main () { int x = boost::bind (G,_1, 4, 8)(2); } ----------- g++ -fsyntax-only -I../ -I../../src TestScale.cc TestScale.cc: In function ‘int main()’: TestScale.cc:14: error: no match for call to ‘(boost::_bi::bind_t<int, int (*)(int, int, int), boost::_bi::list3<boost::arg<1>, boost::_bi::value<int>, boost::_bi::value<int> > >) (int)’ /usr/include/boost/bind/bind_template.hpp:17: note: candidates are: typename boost::_bi::result_traits<R, F>::type boost::_bi::bind_t<R, F, L>::operator()() [with R = int, F = int (*)(int, int, int), L = boost::_bi::list3<boost::arg<1>, boost::_bi::value<int>, boost::_bi::value<int> >] /usr/include/boost/bind/bind_template.hpp:23: note: typename boost::_bi::result_traits<R, F>::type boost::_bi::bind_t<R, F, L>::operator()() const [with R = int, F = int (*)(int, int, int), L = boost::_bi::list3<boost::arg<1>, boost::_bi::value<int>, boost::_bi::value<int> >] /usr/include/boost/bind/bind_template.hpp:29: note: typename boost::_bi::result_traits<R, F>::type boost::_bi::bind_t<R, F, L>::operator()(A1&) [with A1 = int, R = int, F = int (*)(int, int, int), L = boost::_bi::list3<boost::arg<1>, boost::_bi::value<int>, boost::_bi::value<int> >] /usr/include/boost/bind/bind_template.hpp:35: note: typename boost::_bi::result_traits<R, F>::type boost::_bi::bind_t<R, F, L>::operator()(A1&) const [with A1 = int, R = int, F = int (*)(int, int, int), L = boost::_bi::list3<boost::arg<1>, boost::_bi::value<int>, boost::_bi::value<int> >]

3 3

FW: [Xpressive] quantify embedded regex - still no joy
by BRIDGES Dick 25 Oct '05

25 Oct '05

<update> The preprocessed source zip was too big so I removed it and am re-sending. I can e-mail the file if it would be useful. I ran the softfloat ARM cross-comiler against the exemplar and it compiled. Problem seems to be the x86 gcc 3.4.2 compiler? </update> -----Original Message----- From: BRIDGES Dick Sent: Tuesday, October 25, 2005 9:13 AM To: 'boost(a)lists.boost.org' Subject: RE: [boost] [Xpressive] quantify embedded regex - still no joy > -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of Eric Niebler > Sent: Monday, October 24, 2005 4:56 PM > To: boost(a)lists.boost.org > Subject: Re: [boost] [Xpressive] How to quantify embedded regex? > > > BRIDGES Dick wrote: > > I am trying to use Xpressive for parsing string-based > message buffers. > > The messages start with a fixed string and end with an "empty" line > > (similar in form to HTTP). Here is code that illustrates > my problem: > > > <snip> > > You're doing it right, and the commented out lines compile > for me (with > VC++ 7.1). I recently fixed a few bugs in this area, so perhaps you > could give the latest version (0.9.8a from Oct 19) a shot and let me > know if that works. <snip> > -- > Eric Niebler > Boost Consulting > www.boost-consulting.com I cleaned out the old version then installed 0.9.8a but I still get the same error on the same line: sregex re_ = "FROGGIE" >> _ln >> +(name_value_pair_) >> _ln; I'm going to try cross-compiling (the *real* target) this exemplar but that will take me a while to set up. In the meantime the error text and preprocessed source (zipped) from the most recent attempt are attached. I certainly appreciate your help with this. Regards, Dick Bridges

2 1

Boost regression notification (2005-10-25 [HEAD])
by Douglas Gregor 25 Oct '05

25 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-25T05:00:11Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 473 failures in 13 libraries: concept_check (13) date_time (2) graph (2) mpl (1) parameter (3) python (1) serialization (36) spirit (10) thread (4) tuple (1) type_traits (371) typeof (21) xpressive (8) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |date_time| testwcustom_time_zone: gcc-2.95.3-linux testwposix_time_zone: gcc-2.95.3-linux |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| efficiency: msvc sfinae: msvc tutorial: gcc-2.95.3-linux |python| exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos select_p_with_rule_debug: vc-7_1 switch_problem_debug: gcc-3_4_3-sunos vc-7_1 switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tr1_add_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_add_cv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_add_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_add_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_add_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_aligned_storage_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_alignment_of_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_extent_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_has_nothrow_assign_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_has_nothrow_constr_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_has_nothrow_copy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_has_trivial_assign_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_has_trivial_constr_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_has_trivial_copy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_has_trivial_destructor_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_has_virtual_destructor_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_abstract_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_arithmetic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_array_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_base_of_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_class_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_compound_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_convertible_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_empty_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_enum_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_floating_point_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_function_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_fundamental_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_integral_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_member_func_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_member_obj_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_member_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_object_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_pod_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_polymorphic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_same_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_scalar_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_signed_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_union_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_unsigned_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_void_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_rank_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_remove_all_extents_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_remove_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_remove_cv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_remove_extent_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_remove_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_remove_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_remove_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3: gcc-3.4.4-linux test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5: gcc-3.4.4-linux test5u: gcc-3_3-darwin test6: gcc-3.4.4-linux test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

[Boost-bugs] [ boost-Bugs-1337412 ] Compiler warning with gcc on Linux
by SourceForge.net 25 Oct '05

25 Oct '05

Bugs item #1337412, was opened at 2005-10-25 05:52 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1337412&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: serialization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Robert Ramey (ramey) Summary: Compiler warning with gcc on Linux Initial Comment: I get the following warning compiling on Linux with gcc. No mater what I do I can't seem to get around the warning. Any ideas? Thanks! g++ -c -pipe -Wall -W -g -fPIC -I/usr/lib/qt-3.1/mkspecs/default -I. -I. -Iinclude -Isrc -I../ccbus -I/usr/lib/qt-3.1/include -I.ui/ -I.moc/ -o .obj/TraderButtonKey.o src/TraderButtonKey.cpp /usr/include/boost/archive/detail/common_iarchive.hpp: In member function `void boost::archive::detail::common_iarchive<Archive>::init() [with Archive = boost::archive::text_iarchive]': /usr/include/boost/archive/text_iarchive.hpp:69: instantiated from `boost::archive::text_iarchive_impl<Archive>::text_iarchive_impl(std::istream&, unsigned int) [with Archive = boost::archive::text_iarchive]' /usr/include/boost/archive/text_iarchive.hpp:82: instantiated from here /usr/include/boost/archive/detail/common_iarchive.hpp:75: warning: choosing ` boost::archive::version_type::operator unsigned int&()' over ` boost::archive::version_type::operator unsigned int() const' /usr/include/boost/archive/detail/common_iarchive.hpp:75: warning: for conversion from `boost::archive::version_type' to `unsigned int' /usr/include/boost/archive/detail/common_iarchive.hpp:75: warning: because conversion sequence for the argument is better Code fragment: class TraderButtonKey { public: //! Default constructor. TraderButtonKey( ) : m_cls(0), m_number(0) {} //! Constructor. //! //! \param cls the class //! \param number the number TraderButtonKey( int cls, int number ) : m_cls(cls), m_number(number) {} ... private: //! Required by the boost C++ libraries to provide serialization to //! and from the archive. //! //! \param ar archive to save/load object members //! \param version boost class version template<class Archive> void serialize( Archive & ar, const unsigned int version ) { if (version) // gets rid of unused parameter warning ; ar & m_cls; ar & m_number; } int m_cls; //!< class of the key int m_number; //!< number within that class }; ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1337412&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Xpressive] How to quantify embedded regex?
by BRIDGES Dick 24 Oct '05

24 Oct '05

I am trying to use Xpressive for parsing string-based message buffers. The messages start with a fixed string and end with an "empty" line (similar in form to HTTP). Here is code that illustrates my problem: int main(int argc, char **argv) { std::string buffer_ = "FROGGIE\r\n" "Volume = 3\r\n" "Other1= 0\r\n" "Channel=1\r\n" "Other =2\r\n" "\r\n" "FROGGIE\r\n" "Volume = 4\r\n" "Other1= 8\r\n" "Channel=5\r\n" "Other =3\r\n" "\r\n" "FROGGIE\r\n" "Volume = 4\r\n" "Other1= 8\r\n" "Channel=5\r\n"; // mark_tag name_(1), value_(2); To be used in the name_value_pair later. sregex name_value_pair_ = +alnum >> *_s >> "=" >> *_s >> +_d >> *_s >> _ln; sregex re_ = "FROGGIE" >> _ln >> name_value_pair_ >> _ln; // sregex re_ = "FROGGIE" >> _ln >> repeat<1,5>(name_value_pair_) >> _ln; // sregex re_ = "FROGGIE" >> _ln >> +(name_value_pair_) >> _ln; } The only examples of repeating an embedded regex I could find in the .pdf or the examples subdirectory used predefined regexes like alnum but still, it looked to me that the lines that are commented out should have worked. I am clearly wrong. Both of these forms create very long error messages that end with "internal compiler error". One of those error messages is included as an attachment. The uncommented line compiles fine. Since I'm not very accomplished at regular expressions, maybe I should point out that, besides being able to extract the name/value pairs from each message in turn, I want to use what.suffix() to identify the partial message at the end of the buffer. OS is Linux Core 3 2.6.9-1.667. Compiler is gcc 3.4.2 20041017 (Red Hat 3.4.2-6fc5). Xpressive README (in the .zip) says "Last Modified: October 9, 2005". If someone could point me in the right direction, I'd surely appreciate it. If this query is not appropriate for this group, should I post it to boost-users(a)lists.boost.org or mail the author directly or..? Regards, Dick Bridges

2 1

Re: [boost] boost::dynamic_array
by Martin Bonner 24 Oct '05

24 Oct '05

----Original Message---- From: Boris [mailto:boris@gtemail.net] Sent: 04 October 2005 13:18 To: boost(a)lists.boost.org Subject: Re: [boost] boost::dynamic_array > The reason why I don't want to use std::vector in the project I work > on is that I need a two-dimensional array. Two-dimensional means that > the array stores not only the length but also width and height. > Additionally its elements can be accessed with operator()(size_t > column, size_t row). Now I could derive my two-dimensional array from > std::vector but that doesn't make much sense because how should the > dimensions change when someone calls push_back()? A fixed-size array > whose size can be set a runtime would be an ideal candidate to derive > my two-dimensional array from. For all arrays with more than one > dimension std::vector isn't probably an ideal parent class. So don't /derive/ from std::vector, /contain/ a std::vector instead (and forward the appropriate calls to it). It's really not very difficult (particularly as you don't need to both with eg any of the 'insert' overloads). -- 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 regression notification (2005-10-24 [RC_1_33_0])
by Douglas Gregor 24 Oct '05

24 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-24T14:27:10Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 28 failures in 5 libraries: parameter (2) range (3) serialization (18) spirit (1) variant (4) |parameter| tutorial: borland-5_6_4 gcc-2.95.3-linux |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_shared_ptr_132_text_warchive: intel-win32-8_1 test_shared_ptr_binary_archive: borland-5_6_4 test_shared_ptr_binary_archive_dll: borland-5_6_4 test_shared_ptr_text_archive: borland-5_6_4 test_shared_ptr_text_archive_dll: borland-5_6_4 test_shared_ptr_text_warchive: borland-5_6_4 test_shared_ptr_text_warchive_dll: borland-5_6_4 test_shared_ptr_xml_archive: borland-5_6_4 test_shared_ptr_xml_archive_dll: borland-5_6_4 test_shared_ptr_xml_warchive: borland-5_6_4 test_shared_ptr_xml_warchive_dll: borland-5_6_4 |spirit| for_p_as_parser_tests: mingw-3_4_2 |variant| variant_test1: mingw-3_4_2 variant_test2: mingw-3_4_2 variant_test3: mingw-3_4_2 variant_test4: mingw-3_4_2

2 1

RTL
by Arkadiy Vertleyb 24 Oct '05

24 Oct '05

Hi All. I updated the recently discussed RTL example to demonstrate the performance gain that can be achieved by using the RTL transaction mechanism. The original query, that involves a self-join of the ~20,000 row table on a complex condition, currently takes ~79 sec. on my setup (1.5 Ghz, MinGW, g++ -O2). Then a record is removed from the table, which invalidates all the indexes built by that point. The transaction commit repairs indexes, and the query is re-run. Update, commit, and re-run together take just 1 sec. Please take the example and the updated library (again, a few performance issues were fixed) at the usual location: http://www.boost-consulting.com/vault/index.php?&direction=0&order=&director y=RTL Please note that the directory structure of the library has been "boostified" so please ajust you include path accordingly (although I haven't yet put "boost/rtl" into #include statements, so it should go into the include path for now). Regards, Arkadiy

3 33

[MPL.Math] More major changes.
by Cromwell Enage 24 Oct '05

24 Oct '05

A new directory, boost/mpl/math/unsigned_big_integral_, holds everything pertaining to unsigned_big_integral. The corresponding tag and forward declaration also have their own header files now. Also, enlarge_integral and its forward declaration have their own files as well. This should maximize decoupling of the three entities. The big_integral.cpp example and test programs have been updated to reflect these changes. As for double, whole_part and rational_part have been improved, but you'll need to #include unsigned_big_integral and rational to use them. Major limitation: attempting to calculate the rational_part of any double smaller than 1e+30 will most likely break your compiler's back; unsigned_big_integral and rational still won't mix. Play around with the double.cpp example program at your own risk. Cromwell D. Enage __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

1 0

[ongoing review of binary_int] reviewers for small utility wanted
by Pavel Vozenilek 24 Oct '05

24 Oct '05

Reviews of binary int utility are needed. The tool is very small (but useful) and review should not take much of time. Both Scott Schurr and Matt Calabrese put quite a lot of effort into their work. Scott Schurr's version is in http://boost-consulting.com/vault/ (file binary_int.zip). It can be used as: unsigned int regValue2 = binary_int<1000,1001,0011,0000>::value; Matt Calabrese's version is in http://www.illegal-immigration.com/Riv/boost/binary_literal2.hpp. It can be used as: int x = BOOST_BINARY_LITERAL( 101 0111 1010 0110 ); /Pavel

8 22

Boost regression notification (2005-10-24 [HEAD])
by Douglas Gregor 24 Oct '05

24 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-24T05:00:22Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 523 failures in 12 libraries: concept_check (13) graph (2) mpl (1) parameter (3) python (55) serialization (36) spirit (8) thread (4) tuple (1) type_traits (371) typeof (21) xpressive (8) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| efficiency: msvc sfinae: msvc tutorial: gcc-2.95.3-linux |python| andreas_beyer: vc-7_1 args: vc-7_1 auto_ptr: vc-7_1 back_reference: vc-7_1 ben_scott1: vc-7_1 bienstman1: vc-7_1 bienstman2: vc-7_1 bienstman3: vc-7_1 builtin_converters: vc-7_1 callbacks: vc-7_1 const_argument: vc-7_1 crossmod_exception: vc-7_1 data_members: vc-7_1 defaults: vc-7_1 dict: vc-7_1 docstring: vc-7_1 enum: vc-7_1 exception_translator: vc-7_1 exec: intel-win32-9_0 extract: vc-7_1 implicit: vc-7_1 injected: vc-7_1 iterator: vc-7_1 keywords: vc-7_1 list: vc-7_1 long: vc-7_1 minimal: vc-7_1 multi_arg_constructor: vc-7_1 nested: vc-7_1 numpy: vc-7_1 object: vc-7_1 opaque: vc-7_1 operators: vc-7_1 pearu1: vc-7_1 pickle1: vc-7_1 pickle2: vc-7_1 pickle3: vc-7_1 pickle4: vc-7_1 pointer_vector: vc-7_1 polymorphism: vc-7_1 polymorphism2: vc-7_1 polymorphism2_auto_ptr: vc-7_1 properties: vc-7_1 raw_ctor: vc-7_1 return_arg: vc-7_1 shared_ptr: vc-7_1 slice: vc-7_1 staticmethod: vc-7_1 str: vc-7_1 test_pointer_adoption: vc-7_1 try: vc-7_1 tuple: vc-7_1 vector_indexing_suite: vc-7_1 virtual_functions: vc-7_1 wrapper_held_type: vc-7_1 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tr1_add_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_add_cv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_add_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_add_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_add_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_aligned_storage_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_alignment_of_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_extent_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_has_nothrow_assign_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_has_nothrow_constr_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_has_nothrow_copy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_has_trivial_assign_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_has_trivial_constr_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_has_trivial_copy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_has_trivial_destructor_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_has_virtual_destructor_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_abstract_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_arithmetic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_array_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_base_of_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_class_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_compound_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_convertible_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_empty_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_enum_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_floating_point_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_function_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_fundamental_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_integral_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_member_func_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_member_obj_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_member_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_object_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_pod_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_polymorphic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_same_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_scalar_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_signed_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_union_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_unsigned_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_void_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_is_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_rank_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_remove_all_extents_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_remove_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_remove_cv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_remove_extent_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_remove_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_remove_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 tr1_remove_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3: gcc-3.4.4-linux test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5: gcc-3.4.4-linux test5u: gcc-3_3-darwin test6: gcc-3.4.4-linux test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

[Boost-bugs] [ boost-Support Requests-1336312 ] Unable to build boost with Dinkumware STL version 4.02
by SourceForge.net 24 Oct '05

24 Oct '05

Support Requests item #1336312, was opened at 2005-10-24 05:19 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=1336312&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: smart_ptr Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Peter Dimov (pdimov) Summary: Unable to build boost with Dinkumware STL version 4.02 Initial Comment: I would like to build boost with Dinkumware's STL version 4.02. I do not know how to do this. I am using MS VC 6.0 with sp6.0 and ran into thread safety issues in MSVC 's STL. That was the reason I switched over to the Dinkumware's STL 4.02. Please let me know the correct procedure for building boost libs with this third party STL Thanks. Rashmi. rashmiramalingam(a)yahoo.com ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1336312&group_… ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Bounded types
by Robert Kawulak 24 Oct '05

24 Oct '05

Hi group, Some time ago I've written a set of class templates for bounded types (types whose variables may hold a value only from within a specified range). You can download the sources at http://www.rk.w.pl/progz/bounded. I've created a thread in comp.lang.c++.moderated (http://groups-beta.google.com/group/comp.lang.c++.moderated/browse_frm/thre ad/0298fc4ac6c6d223/) as I was hoping to work the project on and maybe transform it into a proposal for the C++0x standard library, but unfortunately the feedback was very low. Just today I saw in this newsgroup a thread titled "Checked Integral Class" concerning a very similar facility so I'm writing this post to call attention to my implementation. Maybe it would be better to include such class templates in Boost first, and then think about making a proposal for the C++ standard... Unfortuantely there's no documentation yet as this is only a sketch for further refinements, but comments in the code and posts in comp.lang.c++.moderated may answer some of your questions about design decisions and usage. If not then please ask them here or on comp.lang.c++.moderated. Any comments and suggestions are welcome. I hope there are more people who need such a facility and would like to work on it, let's finally do it - C++ lacks bounded types and it's high time to fix that! ;-) Best regards, Robert Kawulak -=##############=- <gg> 6934572 </gg> <gsm> 603654215 </gsm> <www> www.rk.w.pl </www> -=##############=- "I know not with what weapons World War III will be fought, but World War IV will be fought with sticks and stones." - Albert Einstein

14 70

Boost regression notification (2005-10-23 [RC_1_33_0])
by Douglas Gregor 23 Oct '05

23 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-23T14:03:24Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 27 failures in 4 libraries: parameter (2) range (3) serialization (19) variant (3) |parameter| tutorial: borland-5_6_4 gcc-2.95.3-linux |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_inclusion: mingw-3_4_2 test_shared_ptr_132_text_warchive: intel-win32-8_1 test_shared_ptr_binary_archive: borland-5_6_4 test_shared_ptr_binary_archive_dll: borland-5_6_4 test_shared_ptr_text_archive: borland-5_6_4 test_shared_ptr_text_archive_dll: borland-5_6_4 test_shared_ptr_text_warchive: borland-5_6_4 test_shared_ptr_text_warchive_dll: borland-5_6_4 test_shared_ptr_xml_archive: borland-5_6_4 test_shared_ptr_xml_archive_dll: borland-5_6_4 test_shared_ptr_xml_warchive: borland-5_6_4 test_shared_ptr_xml_warchive_dll: borland-5_6_4 |variant| variant_test2: mingw-3_4_2 variant_test5: mingw-3_4_2 variant_test6: mingw-3_4_2

1 0

Boost regression notification (2005-10-23 [HEAD])
by Douglas Gregor 23 Oct '05

23 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-23T05:00:14Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 462 failures in 12 libraries: concept_check (13) graph (2) mpl (1) parameter (3) python (1) serialization (36) spirit (8) thread (4) tuple (1) type_traits (364) typeof (21) xpressive (8) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| efficiency: msvc sfinae: msvc tutorial: gcc-2.95.3-linux |python| exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| add_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 add_cv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 add_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 add_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 add_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 aligned_storage_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 alignment_of_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 extent_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 has_nothrow_assign_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 has_nothrow_constr_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 has_nothrow_copy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 has_trivial_assign_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 has_trivial_constr_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 has_trivial_copy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 has_trivial_destructor_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 has_virtual_destructor_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_abstract_test: gcc-3.4.4-linux intel-win32-9_0 is_arithmetic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_array_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_base_of_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_class_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_compound_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_convertible_test: gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_empty_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_enum_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_floating_point_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_function_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_fundamental_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_integral_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_member_func_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_member_obj_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_member_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_object_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_pod_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_polymorphic_test: gcc-2.95.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_same_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_scalar_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_signed_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_union_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_unsigned_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_void_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 is_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 rank_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 remove_all_extents_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 remove_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 remove_cv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 remove_extent_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 remove_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 remove_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 remove_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 tr1_add_const_test: vc-7_1 tr1_add_cv_test: vc-7_1 tr1_add_pointer_test: vc-7_1 tr1_add_reference_test: vc-7_1 tr1_add_volatile_test: vc-7_1 tr1_aligned_storage_test: vc-7_1 tr1_alignment_of_test: vc-7_1 tr1_extent_test: vc-7_1 tr1_has_nothrow_assign_test: vc-7_1 tr1_has_nothrow_constr_test: vc-7_1 tr1_has_nothrow_copy_test: vc-7_1 tr1_has_trivial_assign_test: vc-7_1 tr1_has_trivial_constr_test: vc-7_1 tr1_has_trivial_copy_test: vc-7_1 tr1_has_trivial_destructor_test: vc-7_1 tr1_has_virtual_destructor_test: vc-7_1 tr1_is_abstract_test: vc-7_1 tr1_is_arithmetic_test: vc-7_1 tr1_is_array_test: vc-7_1 tr1_is_base_of_test: vc-7_1 tr1_is_class_test: vc-7_1 tr1_is_compound_test: vc-7_1 tr1_is_const_test: vc-7_1 tr1_is_convertible_test: vc-7_1 tr1_is_empty_test: vc-7_1 tr1_is_enum_test: vc-7_1 tr1_is_floating_point_test: vc-7_1 tr1_is_function_test: vc-7_1 tr1_is_fundamental_test: vc-7_1 tr1_is_integral_test: vc-7_1 tr1_is_member_func_test: vc-7_1 tr1_is_member_obj_test: vc-7_1 tr1_is_member_pointer_test: vc-7_1 tr1_is_object_test: vc-7_1 tr1_is_pod_test: vc-7_1 tr1_is_pointer_test: vc-7_1 tr1_is_polymorphic_test: vc-7_1 tr1_is_reference_test: vc-7_1 tr1_is_same_test: vc-7_1 tr1_is_scalar_test: vc-7_1 tr1_is_signed_test: vc-7_1 tr1_is_union_test: vc-7_1 tr1_is_unsigned_test: vc-7_1 tr1_is_void_test: vc-7_1 tr1_is_volatile_test: vc-7_1 tr1_rank_test: vc-7_1 tr1_remove_all_extents_test: vc-7_1 tr1_remove_const_test: vc-7_1 tr1_remove_cv_test: vc-7_1 tr1_remove_extent_test: vc-7_1 tr1_remove_pointer_test: vc-7_1 tr1_remove_reference_test: vc-7_1 tr1_remove_volatile_test: vc-7_1 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3: gcc-3.4.4-linux test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5: gcc-3.4.4-linux test5u: gcc-3_3-darwin test6: gcc-3.4.4-linux test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

BOOST_WORKAROUND and g++ -Wundef
by Angus Leeming 23 Oct '05

23 Oct '05

Compiling the attached code with g++ 3.4.4 as g++ -Wundef -Iboost/cvs -o trial trial.cpp produces a heap of warnings warning: "__BORLANDC__" is not defined warning: "_MSC_FULL_VER" is not defined warning: "__MWERKS__" is not defined The warnings are produced by code like: #if BOOST_WORKAROUND(__MWERKS__, BOOST_TESTED_AT(0x3003)) and are, of course, silenced by: #if defined(__MWERKS__) && \ BOOST_WORKAROUND(__MWERKS__, BOOST_TESTED_AT(0x3003)) Grepping around the boost sources, I see that my 'fix' has been applied about 70 times already in the 1260 uses of BOOST_WORKAROUND. Assuming that the lack of consistency reflects only the size of the task, I've made a patch applying the fix to Boost.Random. Chipping away at the block... Hoping that this is useful, Angus

4 16

regex - linking problem
by John Smith 23 Oct '05

23 Oct '05

Dear All, I have a problem linking with regex that I couldn't resolve - would greatly appreciate if anyone could give me a hint. I followed the discussion threads regarding similar problems and got forward with resolving other issues, however this final single problem I could not resolve: error LNK2001: unresolved external symbol "void __cdecl boost::re_detail::raise_runtime_error(class _STL::runtime_error const &)" (?raise_runtime_error@re_detail@boost@@YAXABVruntime_error@_STL@@@Z) My environment: o Windows XP o Microsoft DevStudio - Visual C++ 6, Service pack 6 o I am building my DLL, which will use boost::regex as (an additional) DLL o My build flags - Multithreaded dll (more info is avail if needed) o I am using stlport (which is located on my environment under '...\VC98\Include\stlport\...') o I include <boost/regex.hpp> and using 'boost::wregex', 'boost::wcmatch', 'boost::regex_search', etc o I added the next to 'user.hpp': #define BOOST_REGEX_NO_W32 #define BOOST_REGEX_NO_LIB o I am adding boost library to my linking process with the next pragma statement: #ifdef _DEBUG #pragma comment(lib, "<...the path...>\\boost_regex-vc6-mt-gdp-1_33") #else #pragma comment(lib, "<...the path...>\\boost_regex-vc6-mt-p-1_33") #endif // _DEBUG boost::regex build: o I use BJame.exe to build boost o I call 'VCVars32.bat' before all o I set the next environment variables before calling BJam: * VISUALC=<..the path to 'VC98'...> * INCLUDE=%STLPORT_PATH%;%INCLUDE% o Build line: BJam.exe -a -sTOOLS=MSVC-STLPORT --with-regex ...after all this: the linker error (unresolved 'raise_runtime_error' as written above) M A N Y T H A N K S ! ! ! Paz _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

3 7

Re: [boost] [Review] of binary_int utility starts
by Cromwell Enage 23 Oct '05

23 Oct '05

Errata: In the example I sent, each binary_int should have had all four template arguments set to 1111. (This is what happens when I deal with hexadecimals for too long.) Cromwell D. Enage __________________________________ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs

1 0

[Review] of binary_int utility starts
by Pavel Vozenilek 22 Oct '05

22 Oct '05

Review of binary_int utility written by Scott Schurr begins today and lasts for 7 days. The utility can be found at http://boost-consulting.com/vault/ file binary_int.zip (8 kB). ===Description=== The class template binary_int allows binary literals to be used at compile time. The template reads a binary literal value comprised of from 1 to 16 comma separated 4-bit units of ones and zeros. Example of use: #include <boost/utility.hpp> unsigned int regValue2 = binary_int<1000,1001,0011,0000>::value; enum { val1 = binary_int<1100,0010>::value, val2 = binary_int<1100,0011>::value }; switch (x) { case binary_int<0110,0001>::value: ... break; case binary_int<0111,0001>::value: ... break; } ===Alternative implementation=== Matt Calabrese had written alternative, using only preprocessor. It can be found at http://www.illegal-immigration.com/Riv/boost/binary_literal.hpp Example of use: BOOST_BINARY_LITERAL( 101 0111 1010 0110 ) (there is no need for ::value, more on http://lists.boost.org/Archives/boost/2005/09/93007.php) ===Open questions in Scott Schurs's library=== * How does it work on 64 bit systems? Could someone try? * Naming: perhaps shorter names could be used (e.g. bits/nibble) * BOOST_WORKAROUND in the code, is it really needed? === Questions for the reviewers=== * Which one of the alternatives fits in Boost better? * What is your evaluation of the implementation(s)? * Do you think the utility should be accepted as a Boost library? /Pavel

6 6

Boost regression notification (2005-10-22 [RC_1_33_0])
by Douglas Gregor 22 Oct '05

22 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-22T14:17:08Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 27 failures in 5 libraries: parameter (2) range (3) serialization (18) thread (1) variant (3) |parameter| tutorial: borland-5_6_4 gcc-2.95.3-linux |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_shared_ptr_132_text_warchive: intel-win32-8_1 test_shared_ptr_binary_archive: borland-5_6_4 test_shared_ptr_binary_archive_dll: borland-5_6_4 test_shared_ptr_text_archive: borland-5_6_4 test_shared_ptr_text_archive_dll: borland-5_6_4 test_shared_ptr_text_warchive: borland-5_6_4 test_shared_ptr_text_warchive_dll: borland-5_6_4 test_shared_ptr_xml_archive: borland-5_6_4 test_shared_ptr_xml_archive_dll: borland-5_6_4 test_shared_ptr_xml_warchive: borland-5_6_4 test_shared_ptr_xml_warchive_dll: borland-5_6_4 |thread| test_thread: intel-win32-8_1 |variant| variant_test2: mingw-3_4_2 variant_test5: mingw-3_4_2 variant_test6: mingw-3_4_2

1 0

Boost regression notification (2005-10-22 [HEAD])
by Douglas Gregor 22 Oct '05

22 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-22T05:00:25Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. conversion Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 418 failures in 14 libraries: concept_check (13) conversion (2) date_time (6) graph (2) mpl (1) parameter (3) python (2) serialization (36) spirit (8) thread (4) tuple (1) type_traits (311) typeof (21) xpressive (8) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |conversion| cast_test: vc-7_1 implicit_cast: vc-7_1 |date_time| testconstrained_value: vc-7_1 testgeneric_period: vc-7_1 testgregorian_calendar: vc-7_1 testint_adapter: vc-7_1 testtime_resolution_traits: vc-7_1 testwrapping_int: vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| efficiency: msvc sfinae: msvc tutorial: gcc-2.95.3-linux |python| builtin_converters: intel-win32-9_0 exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| add_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 add_cv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 add_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 add_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 add_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 aligned_storage_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 alignment_of_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 extent_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_nothrow_assign_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_nothrow_constr_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_nothrow_copy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_trivial_assign_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_trivial_constr_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_trivial_copy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_trivial_destructor_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_virtual_destructor_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_abstract_test: gcc-3.4.4-linux vc-7_1 is_arithmetic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_array_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_base_of_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_class_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_compound_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_convertible_test: gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_empty_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_enum_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_floating_point_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_function_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_fundamental_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_integral_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_member_func_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_member_obj_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_member_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_object_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_pod_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_polymorphic_test: gcc-2.95.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_same_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_scalar_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_signed_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_union_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_unsigned_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_void_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 rank_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_all_extents_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_cv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_extent_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3: gcc-3.4.4-linux test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5: gcc-3.4.4-linux test5u: gcc-3_3-darwin test6: gcc-3.4.4-linux test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

[config] Standard version macros proposal -- Reviving the compiler version macros.
by Rene Rivera 22 Oct '05

22 Oct '05

After reading up on past discussions about what people want from a set of standard macros for compiler identification, I put together a wiki page with past information on the subject and my ideas as to what the consensus is. And basic proposal based on the ideas: http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?BoostConfig Discussion, contributions, funny anecdotes are welcome :-) -- -- 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

5 7

[mpl] weird error using has_xxx.hpp
by Andy Little 22 Oct '05

22 Oct '05

Hi, using VC7.1... In the following the output is 0, whereas it should be 1 . However commenting out either of the first 2 headers makes result correct. Can anyone repeat this in VC7.1? ------------- #include <boost/mpl/modulus.hpp> #include <boost/mpl/apply.hpp> #include <boost/mpl/has_xxx.hpp> namespace my{ template<typename T> struct X{ typedef int tag; }; BOOST_MPL_HAS_XXX_TRAIT_DEF(tag); } int main() { std::cout << my::has_tag<my::X<int> >::value << '\n'; } --------------- cheers Andy Little

2 2

Is portability to pre-standard compiler an issue when considering addition to boost library
by Axter 22 Oct '05

22 Oct '05

If code is proposed to be added to the boost library, and it can not compile on non-compliant (pre-standard) compiler, like VC++ 6.0, would that be a major factor for rejection? I have classes that are fully compliant to the C++ standard, but will not compile on VC++ 6.0, because 6.0 doesn't fully support template logic. Is this a factor in consideration for code addition to the boost library?

2 1

Fw: [Boost-bugs] [ boost-Support Requests-1334003 ] 100s of 'template with C linkage' errors
by Peter Dimov 22 Oct '05

22 Oct '05

Forwarding for archival purposes :-) Michael Hopkins wrote: > On 21/10/05 21:44, "Peter Dimov" <pdimov(a)mmltd.net> wrote: > >> I have no access to Mac OS X, but according to this post: >> >> http://www.pixelglow.com/lists/archive/macstl-dev/2005-February/000015.html >> >> this might be caused by the fact that your Boost headers are in >> /usr/include, because GCC has some heuristic that automatically >> encloses system headers in extern "C" blocks. >> >> http://developer.apple.com/documentation/DeveloperTools/gcc-4.0.0/cpp/Syste… >> eaders.html >> >> > Thanks for this Peter. Putting Boost in /opt/local/include/ has > solved the problem. I wonder if this should be mentioned somewhere > in the darwin Boost docs to stop other people going around the same > loop? > > Michael > > > > > > Web: http://www.hopkins-research.com/ > Phone: +44 (O)781 3467 381

1 0

really dumb bjam (v1) question.
by Robert Ramey 21 Oct '05

21 Oct '05

I want to suppress certain warnings that the GCC compiler generates for serialization tests. This entail adding some switches to the gcc command line. So in my Jamfile I make the following modification: rule run-template ( test-name : sources * : requirements * ) { return [ run <lib>../../test/build/boost_test_exec_monitor $(sources) : # command : # input files : # requirements std::locale-support toolset::require-boost-spirit-support <borland*><*><cxxflags>"-w-8080 -w-8071 -w-8057 -w-8062 -w-8008 -w-0018 -w-8066" <gcc*><*><cxxflags>"-Wno-non-virtual-dtor -Wno-ctor-dtor-privacy" $(requirements) : # test name $(test-name) : # default-build debug ] ; } That is I added the line <gcc... This doesn't seem to produce the desired effect. That is, I don't see the new -W switches on the gcc command line. Any help would be appreicated. Robert Ramey

2 1

How should we deal with access to zero pointers?
by Asger Mangaard 21 Oct '05

21 Oct '05

When writing code that *could* access a zero pointer, should one do the following: 1. Nothing 2. assert 3. Exception. In that case which one? My guess would be 1 since an access violation exception will be thrown any way (on VC++ at least), but now I'm not sure? Regards, Asger Mangaard

3 2

Re: [boost] [Boost-bugs] [ boost-Support Requests-1334003 ] 100s of'template with C linkage' errors
by Peter Dimov 21 Oct '05

21 Oct '05

Michael Hopkins wrote: > On 21/10/05 17:26, "Peter Dimov" <pdimov(a)mmltd.net> wrote: > >> SourceForge.net wrote: >> >>>> I am trying Boost 1.33 on Mac OS X 10.4.2 with XCode >>>> 2.1 and compiling the smart pointer test program. I >>>> get hundreds of "error: template with C linkage" errors >>>> within many of the gcc includes. This happens whether >>>> I am using gcc 3.3 or 4.0. >>>> >>>> More detail available if necessary - please contact me >>>> on michael.hopkins(a)hopkins-research.com. >> >> Yes, I think that we do need more detail, but first please make sure >> that you are compiling as C++ and not as C. :-) >> >> > Peter > > I can see why you would think I was doing that, but I¹m sharing a > project directory with all my C++ code and the compiler output > certainly looks like C++. I suspect that something within the Boost > headers is making the compiler Othink in C rather than C++¹. > > I have attached the smart pointer test program and the full compiler > output from XCode when I try to build using Apple GCC4.0 and Apple > GCC3.3. There is a lot of info here so I have zipped them. > > I completely cleaned the projects before I started the builds. I > thought that maybe some combination of the compiler settings is > causing the problem but the same issue occurs whether I use the > ODevelopment¹ or ODeployment¹ settings which are very different. > > Let me know if you need anything else. I have no access to Mac OS X, but according to this post: http://www.pixelglow.com/lists/archive/macstl-dev/2005-February/000015.html this might be caused by the fact that your Boost headers are in /usr/include, because GCC has some heuristic that automatically encloses system headers in extern "C" blocks. http://developer.apple.com/documentation/DeveloperTools/gcc-4.0.0/cpp/Syste…

1 0

Alternative solution to intermediate results problem of expression templates.
by Korcan Hussein 21 Oct '05

21 Oct '05

Hi I'm not sure if this has already been explored or even in current use but I think I may have come up with an alternative solution to the type deduction of intermediate results from expression templates. Instead of using automatic type erasing technique, take the compile-time parse tree of an intermediate expression and create an exact runtime replica of the expression tree using recursive variant types (using Boost.Variant in C++). The creation of the expression tree can be completely automated. I have tried this myself with promising results. The only (minor) downside is in order to avoid redundant copies of operands the types of the operands must be given but not the structure of the compile-time expression tree itself. Leaf nodes of the recursive variant hold constant references to there elements. I've done quick profile of this against the traditional eager evaluation of overloaded operators and it still is more efficient but tree creation does cost in time slightly. If people are interested I can post code the code for this.

1 0

Math lib docs
by John Maddock 21 Oct '05

21 Oct '05

Hubert, Daryle, I'm trying to figure out how to integrate the docs for the few new additions to Boost.Math that come with the TR1 library into the existing documentation. The new docs use quickbook, and the options appear to be: 1) Leave the existing docs as they are, the minor problem with this is that my addition ends up with it's own library entry under doc/html/index.html, while the rest of you get left out of there as you do now :-( 2) Use quickbook to create a new front page for the Math lib, but otherwise leave the html as it is. The doc/html/index.html would now look right, but the existing html docs would be second-class citizens in the BoostBook generated TOC for the Math lib: they would get a main entry, but no sub-entries, and just a forwarding link to the existing html. 3) Convert the existing docs to quickbook: it's a bit tedious, but surprisingly easy to do, and once you get the hang of it, easier to maintain than html: no honestly it is, not having to quote "<>&" etc code snippets is worth the change alone IMO. I don't mind making the initial changeover, but thereafter you guys would have to be happy maintaining the quickbook source. The main advantages are a coherent look to the docs, automatic TOC, optional PDF generation and so on. There's the potential to integrate the docs for the new complex number inverse trig special functions, with the existing docs for the scalar versions as well, but I haven't looked into that yet. Thoughts? Thanks, John.

2 1

(Nuisance) Warnings
by David Abrahams 21 Oct '05

21 Oct '05

Warnings present a difficult conundrum for Boost. I wonder if there's any way we can come up with a coherent policy, so individual library developers don't have to think through all the issues individually and our users develop consistent expectations. Here's what I know: * Some warnings that are just a nuisance, especially for templated code. For example, I am getting a warning from vc-8 that the implicit assignment operator of a particular class template instantiation couldn't be generated. I expect the availability of implicit assignment in that case to depend on the template parameter. In this case, any class template that can take reference arguments that become members of the class is susceptible. * It's impolite to unconditionally disable warnings that people may count on in their own code. The above is a nuisance for me, but it might be crucial for someone developing ordinary classes. * Some popular compilers (GCC) don't have #pragmas that let us turn off warnings in particular regions of code. On those compilers, there is sometimes no workaround in code; suppressing the warning must be done on the compiler's command-line. We can do it in Boost.Build, but of course that won't help people who are using other build systems. And for those that _are_ using Boost.Build, suppressing warnings at that point can be just as impolite as doing it in code. * Even when in-code workarounds are possible, they're often ugly, and since the workarounds (e.g. #pragmas) can be different for every compiler, they really pile up. So, ideas, anyone? -- Dave Abrahams Boost Consulting www.boost-consulting.com

3 2

Boost regression notification (2005-10-21 [RC_1_33_0])
by Douglas Gregor 21 Oct '05

21 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-21T14:27:09Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 28 failures in 4 libraries: parameter (2) python (5) range (3) serialization (18) |parameter| tutorial: borland-5_6_4 gcc-2.95.3-linux |python| builtin_converters: mingw-3_4_2 try: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_shared_ptr_132_text_warchive: intel-win32-8_1 test_shared_ptr_binary_archive: borland-5_6_4 test_shared_ptr_binary_archive_dll: borland-5_6_4 test_shared_ptr_text_archive: borland-5_6_4 test_shared_ptr_text_archive_dll: borland-5_6_4 test_shared_ptr_text_warchive: borland-5_6_4 test_shared_ptr_text_warchive_dll: borland-5_6_4 test_shared_ptr_xml_archive: borland-5_6_4 test_shared_ptr_xml_archive_dll: borland-5_6_4 test_shared_ptr_xml_warchive: borland-5_6_4 test_shared_ptr_xml_warchive_dll: borland-5_6_4

1 0

Boost regression notification (2005-10-21 [HEAD])
by Douglas Gregor 21 Oct '05

21 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-21T05:00:17Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 410 failures in 12 libraries: concept_check (13) graph (2) mpl (1) parameter (3) python (2) serialization (36) spirit (8) thread (4) tuple (1) type_traits (311) typeof (21) xpressive (8) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| efficiency: msvc sfinae: msvc tutorial: gcc-2.95.3-linux |python| builtin_converters: intel-win32-9_0 exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| add_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 add_cv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 add_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 add_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 add_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 aligned_storage_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 alignment_of_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 extent_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_nothrow_assign_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_nothrow_constr_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_nothrow_copy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_trivial_assign_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_trivial_constr_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_trivial_copy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_trivial_destructor_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_virtual_destructor_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_abstract_test: gcc-3.4.4-linux vc-7_1 is_arithmetic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_array_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_base_of_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_class_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_compound_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_convertible_test: gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_empty_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_enum_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_floating_point_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_function_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_fundamental_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_integral_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_member_func_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_member_obj_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_member_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_object_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_pod_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_polymorphic_test: gcc-2.95.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_same_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_scalar_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_signed_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_union_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_unsigned_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_void_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 rank_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_all_extents_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_cv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_extent_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3: gcc-3.4.4-linux test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5: gcc-3.4.4-linux test5u: gcc-3_3-darwin test6: gcc-3.4.4-linux test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

[Boost-bugs] [ boost-Support Requests-1334003 ] 100s of 'template with C linkage' errors
by SourceForge.net 21 Oct '05

21 Oct '05

Support Requests item #1334003, was opened at 2005-10-21 03:27 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=1334003&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: smart_ptr Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Peter Dimov (pdimov) Summary: 100s of 'template with C linkage' errors Initial Comment: Hi I am trying Boost 1.33 on Mac OS X 10.4.2 with XCode 2.1 and compiling the smart pointer test program. I get hundreds of "error: template with C linkage" errors within many of the gcc includes. This happens whether I am using gcc 3.3 or 4.0. More detail available if necessary - please contact me on michael.hopkins(a)hopkins-research.com. Many thanks Michael ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1334003&group_… ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

2 1

Sun Studio 10 compiler version in sunpro_cc.hpp
by P Holdaway 21 Oct '05

21 Oct '05

When using... /opt/studio10/SUNWspro/bin/CC -V CC: Sun C++ 5.7 Patch 117830-04 2005/09/14 On uname -a SunOS solaris 5.8 Generic_108528-29 sun4u sparc SUNW,Sun-Fire-V250 The compiler works much better when I effectively back out the last patch to this file. Changing... if (__SUNPRO_CC < 0x570) to... if (__SUNPRO_CC <= 0x570) *** boost/config/compiler/sunpro_cc.hpp.orig Tue Mar 22 02:55:03 2005 --- boost/config/compiler/sunpro_cc.hpp Thu Oct 20 18:46:18 2005 *************** *** 57,63 **** # define BOOST_NO_INTEGRAL_INT64_T # endif ! # if (__SUNPRO_CC < 0x570) # define BOOST_NO_TEMPLATE_TEMPLATES // see http://lists.boost.org/MailArchives/boost/msg47184.php // and http://lists.boost.org/MailArchives/boost/msg47220.php --- 57,63 ---- # define BOOST_NO_INTEGRAL_INT64_T # endif ! # if (__SUNPRO_CC <= 0x570) # define BOOST_NO_TEMPLATE_TEMPLATES // see http://lists.boost.org/MailArchives/boost/msg47184.php // and http://lists.boost.org/MailArchives/boost/msg47220.php

2 1

[patch] using boost/version.hpp
by Christophe Prud'homme 21 Oct '05

21 Oct '05

Dear Boosters, I am trying to keep some backward compatibility (for some while) for the boost libraries we use in our codes (ublas for example), and I find that the addition below to boost/version.hpp helps a lot with readability in the code instead of using // BOOST_VERSION % 100 is the sub-minor version // BOOST_VERSION / 100 % 1000 is the minor version // BOOST_VERSION / 100000 is the major version ------------------- define BOOST_VERSION_MAJOR 1 #define BOOST_VERSION_MINOR 33 #define BOOST_VERSION_SUBMINOR 1 #define BOOST_MAKE_VERSION( a,b,c ) ((a)*100000+(b)*100+(c)) #define BOOST_VERSION \ BOOST_MAKE_VERSION(BOOST_VERSION_MAJOR,BOOST_VERSION_MINOR,BOOST_VERSION_SUBMINOR) #define BOOST_IS_VERSION(a,b,c) ( BOOST_VERSION >= BOOST_MAKE_VERSION(a,b,c) ) ---------------------------- In order to test the current version of boost: #if BOOST_IS_VERSION(1,33,0) ... write the code according to the API >= 1.33.0 #else ... write the code according to the API < 1.33.0 #endif would that be of interest ? Best regards C.

3 3

Re: [boost] [Review] of binary_int utility starts
by Scott Schurr 21 Oct '05

21 Oct '05

Reece Dunn wrote: > Have you tried an approach that does not use enums. You can > either use a maximum-size integer: Let me give you a little background. One of my goals for this template is for it to take no space. I've been writing C++ code for embedded systems. It's important to me that the conversion from binary to hex (or whatever) happen entirely at compile time, leaving no trace in the object file. The advantage of enums is that they are guaranteed to occupy no space. If I start using integers, even static const integers, the compiler has the choice of leaving some number of those in the object code. I'm trying to avoid that. At any rate, that's my justification for using enums instead of the largest integer for my calculations. I hope now I'll learn why integers are okay, since there are template metaprogramming experts listening. Thanks for the hints and advice. Scott Schurr

2 1

The mailing list archive is down
by Joe Gottman 21 Oct '05

21 Oct '05

There don't seem to be any real posting there from after September 29. The last header says "You have been unsubscribed from the Boost mailing list". Joe Gottman

2 3

Bug list status
by Marshall Clow 20 Oct '05

20 Oct '05

Two weeks ago: 144 open bugs Last week: 117 open bugs Today: 96 open bugs Thanks to everyone who dealt with the bugs! Here are the currently opened bugs, sorted by assignee. If you think that a bug has been assigned incorrectly, please let me know. P.S. I need someone to fix the bugs in the tokenizer library!! Assignee: agurtovoy <http://sourceforge.net/users/agurtovoy/> Summary: mpl::select2nd on vc6 Bug #: 812263 <http://sourceforge.net/tracker/index.php?func=detail&aid=812263&group_id=75…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: Minor coding issue Bug #: 946917 <http://sourceforge.net/tracker/index.php?func=detail&aid=946917&group_id=75…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: typos in wrapping_int.hpp Bug #: 949189 <http://sourceforge.net/tracker/index.php?func=detail&aid=949189&group_id=75…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: wrong usage of ios_base::narrow Bug #: 989487 <http://sourceforge.net/tracker/index.php?func=detail&aid=989487&group_id=75…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: date_time type conversion warning Bug #: 1069225 <http://sourceforge.net/tracker/index.php?func=detail&aid=1069225&group_id=7…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: std::locale construction slows down convert_to_lower() Bug #: 1178092 <http://sourceforge.net/tracker/index.php?func=detail&aid=1178092&group_id=7…> Assignee: az_sw_dude <http://sourceforge.net/users/az_sw_dude/> Summary: local_adjustor::utc_to_local throws 'Time label invalid' Bug #: 1220011 <http://sourceforge.net/tracker/index.php?func=detail&aid=1220011&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: filesytem::directory_iterator portability Bug #: 735403 <http://sourceforge.net/tracker/index.php?func=detail&aid=735403&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem fails in posix with files containing ':' Bug #: 776146 <http://sourceforge.net/tracker/index.php?func=detail&aid=776146&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: clock is not portable Bug #: 788762 <http://sourceforge.net/tracker/index.php?func=detail&aid=788762&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: Boost::Filesystem fails when last character in path is ':' Bug #: 875970 <http://sourceforge.net/tracker/index.php?func=detail&aid=875970&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::tokenizer implicit typename Bug #: 912368 <http://sourceforge.net/tracker/index.php?func=detail&aid=912368&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: filesystem::directory_iterator returns incorrect listing Bug #: 937606 <http://sourceforge.net/tracker/index.php?func=detail&aid=937606&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: xtime_cmp: use comparison not subtraction Bug #: 993272 <http://sourceforge.net/tracker/index.php?func=detail&aid=993272&group_id=75…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::exists is broken on cygwin Bug #: 1010681 <http://sourceforge.net/tracker/index.php?func=detail&aid=1010681&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem is systematically broken Bug #: 1012135 <http://sourceforge.net/tracker/index.php?func=detail&aid=1012135&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: Don't work multilevel hierarchy of test suites in dll. Bug #: 1076691 <http://sourceforge.net/tracker/index.php?func=detail&aid=1076691&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::native() should reject '/' on non-Win32 Bug #: 1151823 <http://sourceforge.net/tracker/index.php?func=detail&aid=1151823&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::exists has bugs with UNC paths Bug #: 1164057 <http://sourceforge.net/tracker/index.php?func=detail&aid=1164057&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: &#1057;ompilation test/minmax_element_test.cpp failed on Sunpro Bug #: 1165844 <http://sourceforge.net/tracker/index.php?func=detail&aid=1165844&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: Bad XML format outpout Bug #: 1173937 <http://sourceforge.net/tracker/index.php?func=detail&aid=1173937&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: boost::filesystem::equivalent does not work on w98 Bug #: 1235262 <http://sourceforge.net/tracker/index.php?func=detail&aid=1235262&group_id=7…> Assignee: beman_dawes <http://sourceforge.net/users/beman_dawes/> Summary: path and directory_iterator doesn't handle windows root path Bug #: 1259176 <http://sourceforge.net/tracker/index.php?func=detail&aid=1259176&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: no conversion from type to const_type Bug #: 547743 <http://sourceforge.net/tracker/index.php?func=detail&aid=547743&group_id=75…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: EdgeListS = setS for adjacency_list does not work Bug #: 1163077 <http://sourceforge.net/tracker/index.php?func=detail&aid=1163077&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: adjacency_matrix should model BidirectionalGraph Bug #: 1168411 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168411&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA graph adaptors for undirected graphs Bug #: 1168420 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168420&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA adaptors for node_array, edge_array Bug #: 1168424 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168424&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: LEDA graph adaptors do not handle hidden nodes properly Bug #: 1168431 <http://sourceforge.net/tracker/index.php?func=detail&aid=1168431&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Generate patches for Graph bugs in 1.32.0 Bug #: 1169920 <http://sourceforge.net/tracker/index.php?func=detail&aid=1169920&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Investigate other kinds of heaps for dijkstra_shortest_paths Bug #: 1170106 <http://sourceforge.net/tracker/index.php?func=detail&aid=1170106&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: function.hpp breaks assign.hpp Bug #: 1181272 <http://sourceforge.net/tracker/index.php?func=detail&aid=1181272&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: vertex bundle properties do not work with VC++.NET 2003 Bug #: 1190394 <http://sourceforge.net/tracker/index.php?func=detail&aid=1190394&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: BGL graph types do not support allocators Bug #: 1193883 <http://sourceforge.net/tracker/index.php?func=detail&aid=1193883&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: random_vertex/random_edge are unnecessarily inefficient Bug #: 1204684 <http://sourceforge.net/tracker/index.php?func=detail&aid=1204684&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: Document copy_component Bug #: 1204688 <http://sourceforge.net/tracker/index.php?func=detail&aid=1204688&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: reverse_graph and constness of property maps Bug #: 1246336 <http://sourceforge.net/tracker/index.php?func=detail&aid=1246336&group_id=7…> Assignee: dgregor <http://sourceforge.net/users/dgregor/> Summary: html docs frequently missing key words Bug #: 1294420 <http://sourceforge.net/tracker/index.php?func=detail&aid=1294420&group_id=7…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: Miss ' = ParserT()' Bug #: 907299 <http://sourceforge.net/tracker/index.php?func=detail&aid=907299&group_id=75…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: spirit insert_key_actor.hpp Bug #: 1059936 <http://sourceforge.net/tracker/index.php?func=detail&aid=1059936&group_id=7…> Assignee: djowel <http://sourceforge.net/users/djowel/> Summary: Another config correction for Sun C++ Bug #: 1220782 <http://sourceforge.net/tracker/index.php?func=detail&aid=1220782&group_id=7…> Assignee: dlwalker <http://sourceforge.net/users/dlwalker/> Summary: template problems with common_factor.hpp Bug #: 491637 <http://sourceforge.net/tracker/index.php?func=detail&aid=491637&group_id=75…> Assignee: ebf <http://sourceforge.net/users/ebf/> Summary: boost::blank - missing operators Bug #: 1191356 <http://sourceforge.net/tracker/index.php?func=detail&aid=1191356&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: timeconv.inl to_duration() nsec error Bug #: 548104 <http://sourceforge.net/tracker/index.php?func=detail&aid=548104&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Solaris - once.cpp compile error Bug #: 549162 <http://sourceforge.net/tracker/index.php?func=detail&aid=549162&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: pthread_delay_np() parm incorrect Bug #: 551157 <http://sourceforge.net/tracker/index.php?func=detail&aid=551157&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Bosot.Thread.condition(win32).notify_all Bug #: 551308 <http://sourceforge.net/tracker/index.php?func=detail&aid=551308&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: AIX 4.3 SIGSEGV at thread termination Bug #: 551577 <http://sourceforge.net/tracker/index.php?func=detail&aid=551577&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: boost::threads uses msvc only function? Bug #: 568951 <http://sourceforge.net/tracker/index.php?func=detail&aid=568951&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: threads unnecessary #include Bug #: 571615 <http://sourceforge.net/tracker/index.php?func=detail&aid=571615&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: BCB6 throw EExternelException Bug #: 596149 <http://sourceforge.net/tracker/index.php?func=detail&aid=596149&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: thread_cleanup problems Bug #: 649291 <http://sourceforge.net/tracker/index.php?func=detail&aid=649291&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Mac implementation of threads is CPU hog Bug #: 885045 <http://sourceforge.net/tracker/index.php?func=detail&aid=885045&group_id=75…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: condition variables and recursive_mutex Bug #: 1072605 <http://sourceforge.net/tracker/index.php?func=detail&aid=1072605&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: compiler error on Mac implementation of threads Bug #: 1201779 <http://sourceforge.net/tracker/index.php?func=detail&aid=1201779&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: timeconv.inl line 116 copy/paste error Bug #: 1239052 <http://sourceforge.net/tracker/index.php?func=detail&aid=1239052&group_id=7…> Assignee: glassfordm <http://sourceforge.net/users/glassfordm/> Summary: Exception safety in class 'thread' Bug #: 1305885 <http://sourceforge.net/tracker/index.php?func=detail&aid=1305885&group_id=7…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: jam_src build scripts need como --c Bug #: 973310 <http://sourceforge.net/tracker/index.php?func=detail&aid=973310&group_id=75…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: 'failed fileclone' when building with -j on 1.32.0 Bug #: 1102389 <http://sourceforge.net/tracker/index.php?func=detail&aid=1102389&group_id=7…> Assignee: grafik <http://sourceforge.net/users/grafik/> Summary: boost jam problem with parallel builds Bug #: 1234224 <http://sourceforge.net/tracker/index.php?func=detail&aid=1234224&group_id=7…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer fails with wchar_t Bug #: 446155 <http://sourceforge.net/tracker/index.php?func=detail&aid=446155&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer not works with Dinkumware 308 Bug #: 458236 <http://sourceforge.net/tracker/index.php?func=detail&aid=458236&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: Tokenizer.hpp doesn't work with BOOST_ENABLE_ASSERT_HANDLER Bug #: 972406 <http://sourceforge.net/tracker/index.php?func=detail&aid=972406&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: Compiler error for tokenizer on Solaris Bug #: 976241 <http://sourceforge.net/tracker/index.php?func=detail&aid=976241&group_id=75…> Assignee: jbandela <http://sourceforge.net/users/jbandela/> Summary: tokenizer and signed char Bug #: 1003889 <http://sourceforge.net/tracker/index.php?func=detail&aid=1003889&group_id=7…> Assignee: jmaurer <http://sourceforge.net/users/jmaurer/> Summary: Diff in state of mersenne_twister gen between GCC3.41 & CW9 Bug #: 1115124 <http://sourceforge.net/tracker/index.php?func=detail&aid=1115124&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: bug in ublas/storage.hpp Bug #: 1095697 <http://sourceforge.net/tracker/index.php?func=detail&aid=1095697&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: dead links in uBLAS page Bug #: 1169273 <http://sourceforge.net/tracker/index.php?func=detail&aid=1169273&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: Documentation not available on web site: Bug #: 1228242 <http://sourceforge.net/tracker/index.php?func=detail&aid=1228242&group_id=7…> Assignee: joerg_walter <http://sourceforge.net/users/joerg_walter/> Summary: uBLAS::subslice doesn't work Bug #: 1292635 <http://sourceforge.net/tracker/index.php?func=detail&aid=1292635&group_id=7…> Assignee: johnmaddock <http://sourceforge.net/users/johnmaddock/> Summary: Adding boost::is_complex to type_traits.hpp Bug #: 1315712 <http://sourceforge.net/tracker/index.php?func=detail&aid=1315712&group_id=7…> Assignee: jsiek <http://sourceforge.net/users/jsiek/> Summary: invalid result for File Dependency Examp Bug #: 551110 <http://sourceforge.net/tracker/index.php?func=detail&aid=551110&group_id=75…> Assignee: jsiek <http://sourceforge.net/users/jsiek/> Summary: Spelling of Edmonds-Karp-Algorithm Bug #: 1226292 <http://sourceforge.net/tracker/index.php?func=detail&aid=1226292&group_id=7…> Assignee: mark_rodgers <http://sourceforge.net/users/mark_rodgers/> Summary: Cannot compile octonion_test.cpp because of bug in sinc.hpp Bug #: 751269 <http://sourceforge.net/tracker/index.php?func=detail&aid=751269&group_id=75…> Assignee: mark_rodgers <http://sourceforge.net/users/mark_rodgers/> Summary: Cannot compile octonion_test.cpp because of bug in sinc.hpp Bug #: 751289 <http://sourceforge.net/tracker/index.php?func=detail&aid=751289&group_id=75…> Assignee: nobody Summary: failure in boost jam unit tests on cygwin Bug #: 940941 <http://sourceforge.net/tracker/index.php?func=detail&aid=940941&group_id=75…> Assignee: nobody Summary: Can't build on cygwin Bug #: 1145183 <http://sourceforge.net/tracker/index.php?func=detail&aid=1145183&group_id=7…> Assignee: ramey <http://sourceforge.net/users/ramey/> Summary: many 'virtual functions vs. non-virtual destructor' warnings Bug #: 1312222 <http://sourceforge.net/tracker/index.php?func=detail&aid=1312222&group_id=7…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: typo in Boost.Test document Bug #: 629685 <http://sourceforge.net/tracker/index.php?func=detail&aid=629685&group_id=75…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: BOOST_CHECK_CLOSE in Boost Test Library Bug #: 754551 <http://sourceforge.net/tracker/index.php?func=detail&aid=754551&group_id=75…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: BOOST_AUTO_TEST doesn't work across multiple units Bug #: 823589 <http://sourceforge.net/tracker/index.php?func=detail&aid=823589&group_id=75…> Assignee: rogeeff <http://sourceforge.net/users/rogeeff/> Summary: Bug in build via MSVC Solution Bug #: 953876 <http://sourceforge.net/tracker/index.php?func=detail&aid=953876&group_id=75…> Assignee: samuel_k <http://sourceforge.net/users/samuel_k/> Summary: format: assert when parsing invalid pattern Bug #: 1326132 <http://sourceforge.net/tracker/index.php?func=detail&aid=1326132&group_id=7…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: ct_gcd_lcm.hpp compilation error Bug #: 558174 <http://sourceforge.net/tracker/index.php?func=detail&aid=558174&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: test_pool_alloc.cpp not compile CW8.1 Bug #: 586779 <http://sourceforge.net/tracker/index.php?func=detail&aid=586779&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: pool::purge_memory() does not reset next_size Bug #: 984124 <http://sourceforge.net/tracker/index.php?func=detail&aid=984124&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: Borland compiler error with Pool, boost::pool_allocator Bug #: 988124 <http://sourceforge.net/tracker/index.php?func=detail&aid=988124&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: perfomance: memory cleanup for pool takes too long Bug #: 995270 <http://sourceforge.net/tracker/index.php?func=detail&aid=995270&group_id=75…> Assignee: shammah <http://sourceforge.net/users/shammah/> Summary: boost::pool_allocator breaks with vector of vectors Bug #: 1179641 <http://sourceforge.net/tracker/index.php?func=detail&aid=1179641&group_id=7…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: Self division wrong in template rational Bug #: 504411 <http://sourceforge.net/tracker/index.php?func=detail&aid=504411&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: Rational sum not optimal for overflows Bug #: 519635 <http://sourceforge.net/tracker/index.php?func=detail&aid=519635&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: rational operator&lt; can overflow Bug #: 798357 <http://sourceforge.net/tracker/index.php?func=detail&aid=798357&group_id=75…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: boost::rational documentation typos(?) Bug #: 1043616 <http://sourceforge.net/tracker/index.php?func=detail&aid=1043616&group_id=7…> Assignee: turkanis <http://sourceforge.net/users/turkanis/> Summary: no Boolean conversion for boost::rational Bug #: 1239906 <http://sourceforge.net/tracker/index.php?func=detail&aid=1239906&group_id=7…> Assignee: vladimir_prus <http://sourceforge.net/users/vladimir_prus/> Summary: call to split_winmain raises exception for 8-bit locale Bug #: 1206663 <http://sourceforge.net/tracker/index.php?func=detail&aid=1206663&group_id=7…> Assignee: vladimir_prus <http://sourceforge.net/users/vladimir_prus/> Summary: multitoken broken in program_options 1.33 Bug #: 1266877 <http://sourceforge.net/tracker/index.php?func=detail&aid=1266877&group_id=7…> -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

1 0

Boost regression notification (2005-10-20 [RC_1_33_0])
by Douglas Gregor 20 Oct '05

20 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-20T14:19:08Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 34 failures in 4 libraries: parameter (2) python (11) range (3) serialization (18) |parameter| tutorial: borland-5_6_4 gcc-2.95.3-linux |python| builtin_converters: cw-8_3 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux gcc-4_0-darwin mingw-3_4_2 vc-6_5 vc-6_5-stlport vc-7_0 |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_shared_ptr_132_text_warchive: intel-win32-8_1 test_shared_ptr_binary_archive: borland-5_6_4 test_shared_ptr_binary_archive_dll: borland-5_6_4 test_shared_ptr_text_archive: borland-5_6_4 test_shared_ptr_text_archive_dll: borland-5_6_4 test_shared_ptr_text_warchive: borland-5_6_4 test_shared_ptr_text_warchive_dll: borland-5_6_4 test_shared_ptr_xml_archive: borland-5_6_4 test_shared_ptr_xml_archive_dll: borland-5_6_4 test_shared_ptr_xml_warchive: borland-5_6_4 test_shared_ptr_xml_warchive_dll: borland-5_6_4

1 0

Boost regression notification (2005-10-20 [HEAD])
by Douglas Gregor 20 Oct '05

20 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-20T05:00:24Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 104 failures in 11 libraries: concept_check (13) graph (2) mpl (1) parameter (3) python (7) serialization (36) spirit (8) thread (4) tuple (1) typeof (21) xpressive (8) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| efficiency: msvc sfinae: msvc tutorial: gcc-2.95.3-linux |python| builtin_converters: gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3: gcc-3.4.4-linux test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5: gcc-3.4.4-linux test5u: gcc-3_3-darwin test6: gcc-3.4.4-linux test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

Please Quote Responsibly (was: Re: serialization, demo.cpp, error: undefined reference to ...)
by Caleb Epstein 20 Oct '05

20 Oct '05

On 10/19/05, troy d. straszheim <troy(a)resophonic.com> wrote: > [pages and pages of errors, reproduced] Putting my Dave hat on, was it reallly necessary to reproduce the original poster's entire message? -- Caleb Epstein caleb dot epstein at gmail dot com

1 0

Boost regression notification (2005-10-19 [RC_1_33_0])
by Douglas Gregor 19 Oct '05

19 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-19T14:52:11Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 40 failures in 4 libraries: parameter (2) python (17) range (3) serialization (18) |parameter| tutorial: borland-5_6_4 gcc-2.95.3-linux |python| builtin_converters: cw-8_3 cw-9_4 gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.1-linux gcc-4_0-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 vc-6_5 vc-6_5-stlport vc-7_0 vc-7_1 |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_shared_ptr_132_text_warchive: intel-win32-8_1 test_shared_ptr_binary_archive: borland-5_6_4 test_shared_ptr_binary_archive_dll: borland-5_6_4 test_shared_ptr_text_archive: borland-5_6_4 test_shared_ptr_text_archive_dll: borland-5_6_4 test_shared_ptr_text_warchive: borland-5_6_4 test_shared_ptr_text_warchive_dll: borland-5_6_4 test_shared_ptr_xml_archive: borland-5_6_4 test_shared_ptr_xml_archive_dll: borland-5_6_4 test_shared_ptr_xml_warchive: borland-5_6_4 test_shared_ptr_xml_warchive_dll: borland-5_6_4

1 0

Boost regression notification (2005-10-19 [HEAD])
by Douglas Gregor 19 Oct '05

19 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-19T05:00:20Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 115 failures in 11 libraries: concept_check (13) graph (2) mpl (1) parameter (14) python (7) serialization (36) spirit (8) thread (4) tuple (1) typeof (21) xpressive (8) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc tutorial: gcc-2.95.3-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |python| builtin_converters: gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3: gcc-3.4.4-linux test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5: gcc-3.4.4-linux test5u: gcc-3_3-darwin test6: gcc-3.4.4-linux test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

serialization, demo.cpp, error: undefined reference to ...
by Jan Martin Krämer 19 Oct '05

19 Oct '05

Hi, i couldn't fix the problems I had, trying to use serialization in my own code, so I decided to try and compile the demo.cpp file from the tutorial. If i just compile the file it's ok, but if i choose "build project" to create an executable, it fails with a lot of "undefined reference to ...". The specific error messages are in the attachement. I'm using kdevelop with ubuntu (breezy badger) and gcc 4.0.1. I've tried both the boost libraries that come with ubuntu (1.32.0+1.33.0-cvs) and to download and build them manually (boost_1_33_0). I'm not really a c++ guru and i just don't have a clue what I should do. Neither the documentation for the serialization library, nor google were of any help to me. It's probably just a misconfiguration on my part, but I don't know where to look or what to do. I hope you can help, if you need more information I'd be happy to provide it. Jan M. Kraemer __________________________________________________________________________ Erweitern Sie FreeMail zu einem noch leistungsstarkeren E-Mail-Postfach! Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131

2 1

Boost regression notification (2005-10-17 [RC_1_33_0])
by Douglas Gregor 19 Oct '05

19 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-17T14:38:21Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 91 failures in 4 libraries: parameter (2) python (16) range (3) serialization (70) |parameter| tutorial: borland-5_6_4 gcc-2.95.3-linux |python| builtin_converters: cw-8_3 cw-9_4 gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.1-linux gcc-4_0-darwin intel-win32-8_1 mingw-3_4_2 vc-6_5 vc-6_5-stlport vc-7_0 vc-7_1 |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_diamond_binary_archive: gcc-4_0-darwin test_diamond_binary_archive_dll: gcc-4_0-darwin test_diamond_text_archive: gcc-4_0-darwin test_diamond_text_archive_dll: gcc-4_0-darwin test_diamond_text_warchive: gcc-4_0-darwin test_diamond_text_warchive_dll: gcc-4_0-darwin test_diamond_xml_archive: gcc-4_0-darwin test_diamond_xml_archive_dll: gcc-4_0-darwin test_diamond_xml_warchive: gcc-4_0-darwin test_diamond_xml_warchive_dll: gcc-4_0-darwin test_exported_binary_archive: gcc-4_0-darwin test_exported_binary_archive_dll: gcc-4_0-darwin test_exported_text_archive: gcc-4_0-darwin test_exported_text_archive_dll: gcc-4_0-darwin test_exported_text_warchive: gcc-4_0-darwin test_exported_text_warchive_dll: gcc-4_0-darwin test_exported_xml_archive: gcc-4_0-darwin test_exported_xml_archive_dll: gcc-4_0-darwin test_exported_xml_warchive: gcc-4_0-darwin test_exported_xml_warchive_dll: gcc-4_0-darwin test_mult_archive_types: gcc-4_0-darwin test_mult_archive_types_dll: gcc-4_0-darwin test_no_rtti_binary_archive: gcc-4_0-darwin test_no_rtti_binary_archive_dll: gcc-4_0-darwin test_no_rtti_text_archive: gcc-4_0-darwin test_no_rtti_text_archive_dll: gcc-4_0-darwin test_no_rtti_text_warchive: gcc-4_0-darwin test_no_rtti_text_warchive_dll: gcc-4_0-darwin test_no_rtti_xml_archive: gcc-4_0-darwin test_no_rtti_xml_archive_dll: gcc-4_0-darwin test_no_rtti_xml_warchive: gcc-4_0-darwin test_no_rtti_xml_warchive_dll: gcc-4_0-darwin test_shared_ptr_132_binary_archive: gcc-4_0-darwin test_shared_ptr_132_binary_archive_dll: gcc-4_0-darwin test_shared_ptr_132_text_archive: gcc-4_0-darwin test_shared_ptr_132_text_archive_dll: gcc-4_0-darwin test_shared_ptr_132_text_warchive: gcc-4_0-darwin intel-win32-8_1 test_shared_ptr_132_text_warchive_dll: gcc-4_0-darwin test_shared_ptr_132_xml_archive: gcc-4_0-darwin test_shared_ptr_132_xml_archive_dll: gcc-4_0-darwin test_shared_ptr_132_xml_warchive: gcc-4_0-darwin test_shared_ptr_132_xml_warchive_dll: gcc-4_0-darwin test_shared_ptr_binary_archive: borland-5_6_4 gcc-4_0-darwin test_shared_ptr_binary_archive_dll: borland-5_6_4 gcc-4_0-darwin test_shared_ptr_text_archive: borland-5_6_4 gcc-4_0-darwin test_shared_ptr_text_archive_dll: borland-5_6_4 gcc-4_0-darwin test_shared_ptr_text_warchive: borland-5_6_4 gcc-4_0-darwin test_shared_ptr_text_warchive_dll: borland-5_6_4 gcc-4_0-darwin test_shared_ptr_xml_archive: borland-5_6_4 gcc-4_0-darwin test_shared_ptr_xml_archive_dll: borland-5_6_4 gcc-4_0-darwin test_shared_ptr_xml_warchive: borland-5_6_4 gcc-4_0-darwin test_shared_ptr_xml_warchive_dll: borland-5_6_4 gcc-4_0-darwin

4 3

Boost regression notification (2005-10-18 [RC_1_33_0])
by Douglas Gregor 19 Oct '05

19 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-18T15:24:21Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 55 failures in 4 libraries: parameter (2) python (17) range (3) serialization (33) |parameter| tutorial: borland-5_6_4 gcc-2.95.3-linux |python| builtin_converters: cw-8_3 cw-9_4 gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.1-linux gcc-4_0-darwin intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 vc-6_5 vc-6_5-stlport vc-7_0 vc-7_1 |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_class_info_load_binary_archive: cw-9_4 test_class_info_load_binary_archive_dll: cw-9_4 intel-win32-8_1 test_class_info_load_text_archive: cw-9_4 test_class_info_load_text_archive_dll: cw-9_4 intel-win32-8_1 test_class_info_load_text_warchive: cw-9_4 test_class_info_load_text_warchive_dll: cw-9_4 intel-win32-8_1 test_class_info_load_xml_archive: cw-9_4 test_class_info_load_xml_archive_dll: cw-9_4 intel-win32-8_1 test_class_info_load_xml_warchive: cw-9_4 test_class_info_load_xml_warchive_dll: cw-9_4 intel-win32-8_1 test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_shared_ptr_132_text_warchive: intel-win32-8_1 test_shared_ptr_binary_archive: borland-5_6_4 test_shared_ptr_binary_archive_dll: borland-5_6_4 test_shared_ptr_text_archive: borland-5_6_4 test_shared_ptr_text_archive_dll: borland-5_6_4 test_shared_ptr_text_warchive: borland-5_6_4 test_shared_ptr_text_warchive_dll: borland-5_6_4 test_shared_ptr_xml_archive: borland-5_6_4 test_shared_ptr_xml_archive_dll: borland-5_6_4 test_shared_ptr_xml_warchive: borland-5_6_4 test_shared_ptr_xml_warchive_dll: borland-5_6_4

3 2

[TR1 Review] TR1 Formal Review Beginning
by Beman Dawes 19 Oct '05

19 Oct '05

The formal review of the Boost TR1 Library by John Maddock begins today, Saturday, September 24th, and runs through Wednesday, October 5th. The TR1 library provides an implementation of the C++ Technical Report on Standard Library Extensions. This library does not itself implement the TR1 components, rather it's a thin wrapper that will include your standard library's TR1 implementation (if it has one), otherwise it will include the Boost Library equivalents, and import them into namespace std::tr1. Functionality supported includes: * Reference Wrappers * Smart Pointers * Class template result_of. * Function template mem_fn. * Function Object Binders. * Polymorphic function wrappers. * Type Traits. * Random Number Generators and Distributions. * Tuples. * Tuple Interface to std::pair. * Fixed Size Array. * Hash Function Objects. * Regular Expressions. * Complex Number Algorithm Overloads. * Complex Number Additional Algorithms. Functionality in TR1 but not yet available: * Mathematical Special Functions. * Unordered Associative Set (Hash Table). * Unordered Associative Map (Hash Table). * C99 C language additions. Additional information including online documentation is available at http://freespace.virgin.net/boost.regex/tr1/index.html The complete TR1 lib source and docs can be downloaded from http://freespace.virgin.net/boost.regex/tr1/tr1-20050816.zip Please help Boost by posting your formal review of this library. Your comments may be brief or lengthy, but basically the Review Manager needs your evaluation of the library. If you identify problems along the way, please note if they are minor, serious, or showstoppers. Here are some questions you might want to answer in your review: * What is your evaluation of the design? * What is your evaluation of the implementation? * What is your evaluation of the documentation? * What is your evaluation of the potential usefulness of the library? * Did you try to use the library? With what compiler? Did you have any problems? * How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? * Are you knowledgeable about the problem domain? And finally, every review should answer this question: * Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. --Beman Dawes, Review Manager

7 13

Re: [boost] [Review] of binary_int utility starts
by Scott Schurr 19 Oct '05

19 Oct '05

Reece Dunn wrote: > Scott Schurr wrote: > > I'm going to wait until after the review period to start on fixing > > the 64-bit support. Since I don't have a local 64-bit compiler > > I'll be working blind and my first few efforts will be dead wrong. > > The 32-bit microsoft compiler has support for 64-bit literals if you > have version 7.0 or above handy (6.0 might have this, but I haven't > checked). You will need to enable language extensions. I am not sure > about the other compilers, though. > > It should be possible to test the 64-bit stuff on a 32-bit compiler like > VC7 with MS language extensions, or even GCC. > > You may get warnings when converting a 64-bit type to a 32-bit type, or > even a 32-bit type to a 16-bit type. However, the solution for this is: Thanks for the suggestion Reece. I thrashed about some this morning turning on extensions. I'm now able to reproduce the problem that Markus Sch?pflin found: Markus Sch?pflin wrote: > For the next test, I changed struct test_values (in binary_int_test.cpp) to > the following: > > struct test_values { > uint64_t hex_value; > uint64_t bin_value; > }; > > This additionally needs #include <boost/cstdint.hpp>. > > When compiling and running this (on both 32 bit and 64 bit systems), I got > the following error: > > At test_array index 40 8a6c4e20 != ffffffff8a6c4e20 > assertion "test_array[i].hex_value == test_array[i].bin_value" failed: file > "../binary_int_test.cpp", line 118 And I found that... Scott Schurr wrote prematurely: > > At an initial glance it looks like 64-bit support should be > > achievable without heroic efforts. But it certainly won't come > > along for free. I'm using the Microsoft 32-bit Compiler, Version 13.00.9466, and I'm running into two different problems with 64 bit values: 1. So far I've been unable to make Marcus's problem go away. With 32-bit values I was able to fix this up by forcing the underlying type that I write to my enums. When I try this same fix in 64-bits nothing gets better. 2. The worse problem is that binary value values larger than 32 bits (8 nibbles) get their upper nibbles truncated. After a couple of tests it appears that, for this compiler, the largest supported enum value must fit in 32 bits. If that's correct, then my enum based calculations run out of steam on this compiler at 32 bits. Hmmph. Matt Calabrese's macro-based approach is looking more appealing, at least as far as 64-bit support goes. Scott Schurr

5 5

[testing] Refactoring serialization tests, and possibly others.
by Rene Rivera 19 Oct '05

19 Oct '05

After having run two cycles of tests for Boost with the mingw-3_4_2-stlport-5_0 configuration and having it take more than 14 hours on a 2.2Ghz+1GB machine, most of that in the Boost.Serialization library[*]. And reading some of the recent discussion about the desire to expand testing to include cross-version compatibility and cross-compiler compatibility, and hence having the number of tests multiply possibly exponentially. I am seriously concerned that we are going in the wrong direction when it comes to structuring tests. From looking at the tests for serialization I think we are over-testing, and we are past the point of exhausting testing resources. Currently this library takes the approach of carpet bombing the testing space. The current tests follow this overall structure: [feature tests] x [archive types] x [char/wchar] x [DLL/not-DLL] Obviously this will never scale. My first observation is that it doesn't seem that those axis look like independent features to me. That is, for example, the char/wchar functionality doesn't depend on the feature getting tested, or at least it shouldn't. And I can't imagine the library is structure internally in that way. To me it doesn't make sense to test "array" saving with each of the 3 archive types since the code for serialization of the "array" is the same in all situations. Hence it would makes more sense to me to structure the tests as: [feature test] x [xml archive type] x [char] x [not-DLL] [text archive tests] x [char] x [non-DLL] [binary archive tests] x [non-DLL] [wchar tests] x [non-DLL] [DLL tests] Basically it's structured to test specific aspects of the library not to test each aspect against each other aspect. Some benefits as I see them: * Reduced number of tests means faster turn around on testing. * It's much easier to add tests for other aspects as one only has to concentrate on a few tests instead of many likely unrelated aspects. * The tests can be expanded to test the aspects more critically. For example the DLL tests can be very specific as to what aspect of DLL vs non-DLL they test. * It is easier to tell what parts of the library are breaking when the tests are specific. [*] That's just a CPU time observation, not to mention that it takes 2.15GB of disk space out of a total of 5.09GB. And it's only one compiler variation. -- -- 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

5 37

[Boost-bugs] [ boost-Support Requests-1330119 ] building boost sgd libraries
by SourceForge.net 18 Oct '05

18 Oct '05

Support Requests item #1330119, was opened at 2005-10-18 21:08 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=1330119&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: cxgd (cxgd) Assigned to: Nobody/Anonymous (nobody) Summary: building boost sgd libraries Initial Comment: how do I build the boost sgd libraries ? My project requires libboost_thread-vc71-mt-sgd-1_33.lib but I have libboost_thread-vc71-mt-gd-1_33.lib what is the difference between the sgd and the gd libraries ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1330119&group_… ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Boost regression notification (2005-10-18 [HEAD])
by Douglas Gregor 18 Oct '05

18 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-18T05:00:20Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 115 failures in 11 libraries: concept_check (13) graph (2) mpl (1) parameter (14) python (7) serialization (36) spirit (8) thread (4) tuple (1) typeof (21) xpressive (8) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc tutorial: gcc-2.95.3-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |python| builtin_converters: gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 vc-7_1 exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3: gcc-3.4.4-linux test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5: gcc-3.4.4-linux test5u: gcc-3_3-darwin test6: gcc-3.4.4-linux test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

3 3

asio networking proposal 0.3.4
by Christopher Kohlhoff 18 Oct '05

18 Oct '05

Hello all, I have just released asio 0.3.4. You can download it, or view the documentation online, at http://asio.sourceforge.net. The major changes in this version include support for scatter-gather operations, an initial SSL implementation, and documentation improvements including an HTTP 1.0 server example. Code that uses asio will need to be updated. It is my feeling that there are no more major interface changes to be made, and my next goal is to convert asio into "Boost format" in preparation for a submission. Feedback is appreciated. In detail, the changes since asio 0.3.3 include: - Added support for scatter-gather on all read and write operations. These operations now take a list of one or more "buffers" for the operation. These buffers may be created to represent raw memory, POD arrays, boost::array or std::vector. This change breaks existing code, which needs to be fixed as follows. Where one used to write: sock.read(data, length); one now needs to write: sock.read(asio::buffers(data, length)); Similar changes are needed on all read, write, send and receive operations, both synchronous and asynchronous. - Added initial SSL support using OpenSSL. This takes the form of a template, called asio::ssl::stream, which can be used with any class which supports the Sync_*_Stream and Async_*_Stream concepts, e.g.: typedef asio::ssl::stream<asio::stream_socket> my_ssl_socket; Please note that for now this only works when used with single-threaded demuxers. A big thanks to Indrek Juhani of Voipster for developing the core implementation, and to Dirk Griffioen for organising this contribution. - Exceptions in handlers are no longer suppressed using catch (...). Instead they are now allowed to propagate out of the basic_demuxer::run function so they may be caught by application code. After an exception is caught, basic_demuxer::run may be called again immediately to continue processing. - Replaced the basic_demuxer::work_started/work_finished classes with an RAII class called basic_demuxer::work. - Added iostream output operators for ipv4::address, ipv4::tcp::endpoint and ipv4::udp::endpoint. - Added an HTTP 1.0 server example. - Added a kqueue reactor implementation for Mac OS X. Thanks to Stefan Arentz for providing the initial implementation. - Improved error handling in the epoll_reactor. - TSS slot usage has been minimised to use one slot for all demuxers of a given type, rather than one slot per demuxer object. - The calls to WSAStartup and WSACleanup have been made safer with respect to global demuxer objects. - Automaticaly link in ws2_32.lib when using asio on Win32 with Visual C++ or Borland C++. - Added back missing implementation of get_remote_endpoint. - Visual C++ 6 and gcc 2.95.x are not supported in this version, due to lack of testing resources. - Many documentation improvements. Note that I chose not to rename the send/receive family of functions to write and read, as had been discussed. After further thought I came to the conclusion that functions should only have the same name if they provide the same semantics. I think it's fair to say that read and write are the ideal names for the stream concepts' operations. However stream_socket's send and receive functions take additional parameters (flags) that can significantly alter the semantics (e.g. peek). A similar thing applies to not renaming datagram_socket's send/send_to/receive/receive_from functions, which are datagram-oriented, as opposed to the stream concepts' read and write which are (obviously) stream-oriented. Cheers, Chris

4 7

Re: [boost] asio networking proposal 0.3.4
by Martin Bonner 18 Oct '05

18 Oct '05

From: Christopher Kohlhoff [mailto:chris@kohlhoff.com] > >>> struct message { >>> int a; >>> double b; >>> int c_size; >>> char c[0]; >>> }; >>> message* m = ...; >>> sock.write(buffers(m, sizeof(message) + m->c_size)); >> > --- Martin Bonner <martin.bonner(a)pitechnology.com> wrote: >> Oh no! Please! Don't let us encourage bad code like that. > > One person's bad code is another person's necessary performance > optimisation :) > >> It will work if >> the receiving socket belongs to the same program on the same >> machine. Otherwise it depends on: >> - sizeof(int) (16,32,64 bits) >> - endianness >> - representation of double (IEEE or IBM) >> >> ... and that's just the obvious, real-world, differences that can be >> encountered TODAY. > > It will in fact work across different machines that have the same > architecture, where the programs use the same alignment etc. This may > seem picky, but it is a vital point. > > The optimisation shown in the example, ugly though it looks, is in > principle what is used in receiver-makes-right protocols, i.e. the > cost associated with dealing with architecture differences is left to > the receiver. That way if the data is sent between two machines of > the same type, then those costs are eliminated. > > There's a large body of research and experience in these sorts of > optimisations, e.g. MPI, and they are critical to high performance > computing. > > I agree that code like that should not appear in typical applications > and should not be generally encouraged. However there is a use case > for it in domains that would also often use C++ for performance. > Therefore I believe that a C++ networking library must not preclude > such a usage. That seems fair enough (a programmer's gotta do what the profiler says a programmer's gotta do). However, can I put in a plea that we arrange things so that this is not the simplest thing to do? Compare the C file API. The simplest way to read and write a struct to a file, is with a simple call to fread/fwrite. That means too many people just read and writes structs to file as binary, and then hit problems when the next compiler release changes the struct layout. Doing it the right way (with a series of unsigned chars) is hard work (and often doesn't get done). -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

1 0

Re: [boost] asio networking proposal 0.3.4
by Martin Bonner 18 Oct '05

18 Oct '05

> --- Beman Dawes <bdawes(a)acm.org> wrote: >> Where did this idea come from that the only way to avoid an >> additional copy is to use a void *? From: Christopher Kohlhoff [mailto:chris@kohlhoff.com] > It's not just avoiding a copy, it's avoiding a copy *and* allowing > arbitrary data structures to be sent. IMHO an important use case for > C++ and networking is being able to do things like: > > struct message { > int a; > double b; > int c_size; > char c[0]; > }; > message* m = ...; > sock.write(buffers(m, sizeof(message) + m->c_size)); Oh no! Please! Don't let us encourage bad code like that. It will work if the receiving socket belongs to the same program on the same machine. Otherwise it depends on: - sizeof(int) (16,32,64 bits) - endianness - representation of double (IEEE or IBM) ... and that's just the obvious, real-world, differences that can be encountered TODAY. The only safe datatype for transport over a socket is an array of unsigned char with a defined layout. Thus we would need somethink like: message* m = ...; std::vector<unsigned char> mbuf; mbuf.reserver(sizeof(m)+m->c_size); mbuf.push_back( m->a & 0xff ); mbuf.push_back( (m->a >> 8) & 0xff ); pushDouble( mbuf, m->b ); // pushDouble decodes the double and pushes // the bytes of a IEEE double onto mbuf. etc This looks like an application for something like serialization. For example, the result of right shifting a negative number is implementation defined and something more subtle is required for real portability. (Something like serialization, rather than the same as, because the user needs to specify "this field is 16 bits", "this field is 32 bits" independant of the size of the datatype used to store the field). (Or have I missed something terribly subtle in the "buffers" code which handles all this) -- 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

[program_options] typo in doc
by Matt Hurd 17 Oct '05

17 Oct '05

http://www.boost.org/doc/html/program_options/overview.html#id1247613 has the line pd.add("output-file", 2).add_optional("input-file", -1); which is not supported. Only void add(...) exists. pd.add("output-file", 2) pd.add("input-file", -1); would be correct I think. matt.

1 0

Re: [boost] [Review] of binary_int utility starts
by Scott Schurr 17 Oct '05

17 Oct '05

"Reece Dunn" <msclrhd(a)hotmail.com> wrote: > Scott Schurr wrote: > >I suspect that there's a problem with the size of the literals > >on the 64-bit compilers. Does one declare a 64-bit literal by > >appending a double L ('LL')? If so, then I'll give that a try. > > This will depend on the compiler. I am not sure what GCC does, but for MS > (and compatible compilers - Borland, CodeWarrior, Intel and others) you do: > > __int64 biglit = 2i64; > unsigned __int64 biglit2 = 2ui64; > > If GCC has the ll and ull prefixes, you could create a macro for defining > signed/unsigned 64-bit literals either where uint64_t is defined or in > Boost.Config. e.g.: > > uint64_t biglit = MAKE_UINT64_T( 2 ); Thanks for that information. I think what I'll want to do, for a first cut, is always produce 64-bit literals for 64-bit capable compilers. I'm going to wait until after the review period to start on fixing the 64-bit support. Since I don't have a local 64-bit compiler I'll be working blind and my first few efforts will be dead wrong. At an initial glance it looks like 64-bit support should be achievable without heroic efforts. But it certainly won't come along for free. Thanks again Reece. Scott Schurr

2 1

Futures
by Thorsten Schuett 17 Oct '05

17 Oct '05

Hi, I uploaded a new version of the futures library to the boost vault. http://tinyurl.com/9lws4 Just a remainder, futures execute functions in separate threads. Later the future can be used to retrieve the result of the function. The major change is the addition of iterators over futures. Last time some people complained during the discussion that there were operators missing which they needed for combining futures. So instead of adding more operators I added iterators which can be used to implement almost any combination of futures. simple_future<int> f1 = bind(fac, 4); simple_future<int> f1 = bind(fac, 6); simple_future<int> f1 = bind(fac, 8); future<int> f = f1 || f2 || f3; for(future<int>::iterator it = f.begin(); f.end() != it; ++it){ cout << *it << endl; // prints fac(4), fac(6) and fac(8) if(*it > XXX) break; } That way, you can wait for as many futures to finish as you want and you can decide while waiting, for how many you want to wait. All feedback is appreciated. Thanks, Thorsten

3 3

Boost regression notification (2005-10-17 [HEAD])
by Douglas Gregor 17 Oct '05

17 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-17T05:00:22Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. functional array any utility conversion tokenizer dynamic_bitset format integer crc Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 707 failures in 50 libraries: algorithm/minmax (2) any (2) array (5) assign (6) bind (18) concept_check (15) config (5) conversion (2) crc (1) date_time (43) disjoint_sets (1) dynamic_bitset (4) filesystem (7) foreach (11) format (3) function (18) functional (1) functional/hash (19) graph (36) integer (3) iostreams (28) iterator (19) lambda (14) logic (2) mpl (83) multi_array (7) numeric/conversion (2) numeric/interval (11) optional (4) parameter (15) property_map (2) python (50) random (2) rational (1) regex (36) serialization (36) signals (6) smart_ptr (9) spirit (8) static_assert (3) test (17) thread (20) timer (1) tokenizer (6) tuple (3) type_traits (64) typeof (21) utility (15) variant (12) xpressive (8) |algorithm/minmax| minmax: gcc-2.95.3-linux minmax_element: gcc-2.95.3-linux |any| any_test: gcc-2.95.3-linux any_to_ref_test: gcc-2.95.3-linux |array| array1: gcc-2.95.3-linux array2: gcc-2.95.3-linux array3: gcc-2.95.3-linux array4: gcc-2.95.3-linux array5: gcc-2.95.3-linux |assign| basic: gcc-2.95.3-linux list_of: gcc-2.95.3-linux list_of_workaround: gcc-2.95.3-linux static_list_of: gcc-2.95.3-linux std: gcc-2.95.3-linux tuple_list_of: gcc-2.95.3-linux |bind| bind_const_test: gcc-2.95.3-linux bind_cv_test: gcc-2.95.3-linux bind_dm2_test: gcc-2.95.3-linux bind_dm_test: gcc-2.95.3-linux bind_eq_test: gcc-2.95.3-linux bind_function_test: gcc-2.95.3-linux bind_lookup_problem_test: gcc-2.95.3-linux bind_not_test: gcc-2.95.3-linux bind_rel_test: gcc-2.95.3-linux bind_rv_sp_test: gcc-2.95.3-linux bind_stateful_test: gcc-2.95.3-linux bind_test: gcc-2.95.3-linux mem_fn_derived_test: gcc-2.95.3-linux mem_fn_dm_test: gcc-2.95.3-linux mem_fn_eq_test: gcc-2.95.3-linux mem_fn_rv_test: gcc-2.95.3-linux mem_fn_test: gcc-2.95.3-linux mem_fn_void_test: gcc-2.95.3-linux |concept_check| class_concept_check_test: gcc-2.95.3-linux concept_check_test: gcc-2.95.3-linux stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |config| abi_test: gcc-2.95.3-linux config_info: gcc-2.95.3-linux config_link_test: gcc-2.95.3-linux config_test: gcc-2.95.3-linux limits_test: gcc-2.95.3-linux |conversion| cast_test: gcc-2.95.3-linux implicit_cast: gcc-2.95.3-linux |crc| crc_test: gcc-2.95.3-linux |date_time| testc_local_adjustor: gcc-2.95.3-linux testclock: gcc-2.95.3-linux testconstrained_value: gcc-2.95.3-linux testdate: gcc-2.95.3-linux testdate_dll: gcc-2.95.3-linux testdate_duration: gcc-2.95.3-linux testdate_duration_dll: gcc-2.95.3-linux testdate_input_facet: gcc-2.95.3-linux testdate_input_facet_dll: gcc-2.95.3-linux testdate_iterator: gcc-2.95.3-linux testdate_iterator_dll: gcc-2.95.3-linux testdst_rules: gcc-2.95.3-linux testdst_transition_day_rule: gcc-2.95.3-linux testduration: gcc-2.95.3-linux testfiletime_functions: gcc-2.95.3-linux testformatters: gcc-2.95.3-linux testformatters_dll: gcc-2.95.3-linux testgenerators: gcc-2.95.3-linux testgenerators_dll: gcc-2.95.3-linux testgeneric_period: gcc-2.95.3-linux testgreg_cal: gcc-2.95.3-linux testgreg_cal_dll: gcc-2.95.3-linux testgreg_day: gcc-2.95.3-linux testgreg_day_dll: gcc-2.95.3-linux testgreg_duration_operators: gcc-2.95.3-linux testgreg_durations: gcc-2.95.3-linux testgreg_durations_dll: gcc-2.95.3-linux testgreg_month: gcc-2.95.3-linux testgreg_month_dll: gcc-2.95.3-linux testgreg_year: gcc-2.95.3-linux testgreg_year_dll: gcc-2.95.3-linux testint_adapter: gcc-2.95.3-linux testiterator: gcc-2.95.3-linux testlocal_adjustor: gcc-2.95.3-linux testmicrosec_time_clock: gcc-2.95.3-linux testparse_time: gcc-2.95.3-linux testperiod: gcc-2.95.3-linux testperiod_dll: gcc-2.95.3-linux testtime: gcc-2.95.3-linux testtime_formatters: gcc-2.95.3-linux testtime_period: gcc-2.95.3-linux testtime_resolution_traits: gcc-2.95.3-linux testwrapping_int: gcc-2.95.3-linux |disjoint_sets| disjoint_set_test: gcc-2.95.3-linux |dynamic_bitset| dyn_bitset_unit_tests1: gcc-2.95.3-linux dyn_bitset_unit_tests2: gcc-2.95.3-linux dyn_bitset_unit_tests3: gcc-2.95.3-linux dyn_bitset_unit_tests4: gcc-2.95.3-linux |filesystem| convenience_test: gcc-2.95.3-linux default_name_check_test: gcc-2.95.3-linux large_file_support_test: gcc-2.95.3-linux operations_test: gcc-2.95.3-linux operations_test_dll: gcc-2.95.3-linux path_test: gcc-2.95.3-linux path_test_dll: gcc-2.95.3-linux |foreach| array_byref: gcc-2.95.3-linux array_byval: gcc-2.95.3-linux call_once: gcc-2.95.3-linux cstr_byref: gcc-2.95.3-linux cstr_byval: gcc-2.95.3-linux pair_byref: gcc-2.95.3-linux pair_byval: gcc-2.95.3-linux rvalue_nonconst: gcc-2.95.3-linux stl_byref: gcc-2.95.3-linux stl_byval: gcc-2.95.3-linux user_defined: gcc-2.95.3-linux |format| format_test1: gcc-2.95.3-linux format_test2: gcc-2.95.3-linux format_test_wstring: gcc-2.95.3-linux |function| allocator_test: gcc-2.95.3-linux contains2_test: gcc-2.95.3-linux contains_test: gcc-2.95.3-linux function_30: gcc-2.95.3-linux function_arith_cxx98: gcc-2.95.3-linux function_arith_portable: gcc-2.95.3-linux function_n_test: gcc-2.95.3-linux function_ref_cxx98: gcc-2.95.3-linux function_ref_portable: gcc-2.95.3-linux lambda_test: gcc-2.95.3-linux lib_function_test: gcc-2.95.3-linux mem_fun_cxx98: gcc-2.95.3-linux mem_fun_portable: gcc-2.95.3-linux stateless_test: gcc-2.95.3-linux std_bind_cxx98: gcc-2.95.3-linux std_bind_portable: gcc-2.95.3-linux sum_avg_cxx98: gcc-2.95.3-linux sum_avg_portable: gcc-2.95.3-linux |functional| function_test: gcc-2.95.3-linux |functional/hash| books: gcc-2.95.3-linux container_fwd_test: gcc-2.95.3-linux hash_built_in_array_test: gcc-2.95.3-linux hash_custom_test: gcc-2.95.3-linux hash_deque_test: gcc-2.95.3-linux hash_float_test: gcc-2.95.3-linux hash_function_pointer_test: gcc-2.95.3-linux hash_list_test: gcc-2.95.3-linux hash_map_test: gcc-2.95.3-linux hash_number_test: gcc-2.95.3-linux hash_pointer_test: gcc-2.95.3-linux hash_range_test: gcc-2.95.3-linux hash_set_test: gcc-2.95.3-linux hash_string_test: gcc-2.95.3-linux hash_value_array_test: gcc-2.95.3-linux hash_vector_test: gcc-2.95.3-linux link_test: gcc-2.95.3-linux point: gcc-2.95.3-linux portable: gcc-2.95.3-linux |graph| adj_list_cc: gcc-2.95.3-linux adj_matrix_cc: gcc-2.95.3-linux adjacency_matrix_test: gcc-2.95.3-linux astar_search_test: gcc-2.95.3-linux bellman-test: gcc-2.95.3-linux betweenness_centrality_test: gcc-2.95.3-linux bfs: gcc-2.95.3-linux bfs_cc: gcc-2.95.3-linux biconnected_components_test: gcc-2.95.3-linux bundled_properties: gcc-2.95.3-linux copy: gcc-2.95.3-linux cuthill_mckee_ordering: gcc-2.95.3-linux dag_longest_paths: gcc-2.95.3-linux dfs: gcc-2.95.3-linux dfs_cc: gcc-2.95.3-linux dijkstra_cc: gcc-2.95.3-linux dijkstra_heap_performance: gcc-2.95.3-linux edge_list_cc: gcc-2.95.3-linux filtered_graph_cc: gcc-2.95.3-linux floyd_warshall_test: gcc-2.95.3-linux graph: gcc-2.95.3-linux graph_concepts: gcc-2.95.3-linux graphviz_test: vc-7_1 gursoy_atun_layout_test: gcc-2.95.3-linux isomorphism: gcc-2.95.3-linux king_ordering: gcc-2.95.3-linux layout_test: gcc-2.95.3-linux intel-win32-9_0 matching_test: gcc-2.95.3-linux property_iter: gcc-2.95.3-linux relaxed_heap_test: gcc-2.95.3-linux reverse_graph_cc: gcc-2.95.3-linux sequential_vertex_coloring: gcc-2.95.3-linux subgraph: gcc-2.95.3-linux transitive_closure_test: gcc-2.95.3-linux vector_graph_cc: gcc-2.95.3-linux |integer| cstdint_test: gcc-2.95.3-linux integer_test: gcc-2.95.3-linux integer_traits_test: gcc-2.95.3-linux |iostreams| array_test: gcc-2.95.3-linux auto_close_test: gcc-2.95.3-linux buffer_size_test: gcc-2.95.3-linux bzip2_test: gcc-2.95.3-linux component_access_test: gcc-2.95.3-linux compose_test: gcc-2.95.3-linux copy_test: gcc-2.95.3-linux counter_test: gcc-2.95.3-linux example_test: gcc-2.95.3-linux file_descriptor_test: gcc-2.95.3-linux file_test: gcc-2.95.3-linux filtering_stream_test: gcc-2.95.3-linux flush_test: gcc-2.95.3-linux invert_test: gcc-2.95.3-linux line_filter_test: gcc-2.95.3-linux mapped_file_test: gcc-2.95.3-linux newline_test: gcc-2.95.3-linux null_test: gcc-2.95.3-linux pipeline_test: gcc-2.95.3-linux positioning_test: gcc-2.95.3-linux regex_filter_test: gcc-2.95.3-linux restrict_test: gcc-2.95.3-linux seekable_file_test: gcc-2.95.3-linux seekable_filter_test: gcc-2.95.3-linux stdio_filter_test: gcc-2.95.3-linux symmetric_filter_test: gcc-2.95.3-linux tee_test: gcc-2.95.3-linux zlib_test: gcc-2.95.3-linux |iterator| concept_tests: gcc-2.95.3-linux counting_iterator_test: gcc-2.95.3-linux filter_iterator_test: gcc-2.95.3-linux indirect_iter_member_types: gcc-2.95.3-linux indirect_iterator_test: gcc-2.95.3-linux interoperable: gcc-2.95.3-linux is_lvalue_iterator: gcc-2.95.3-linux is_readable_iterator: gcc-2.95.3-linux iterator_adaptor_cc: gcc-2.95.3-linux iterator_adaptor_test: gcc-2.95.3-linux iterator_archetype_cc: gcc-2.95.3-linux iterator_facade: gcc-2.95.3-linux iterator_traits_test: gcc-2.95.3-linux permutation_iterator_test: gcc-2.95.3-linux pointee: gcc-2.95.3-linux reverse_iterator_test: gcc-2.95.3-linux transform_iterator_test: gcc-2.95.3-linux unit_tests: gcc-2.95.3-linux zip_iterator_test: gcc-2.95.3-linux |lambda| algorithm_test: gcc-2.95.3-linux bind_tests_advanced: gcc-2.95.3-linux bind_tests_simple: gcc-2.95.3-linux bind_tests_simple_f_refs: gcc-2.95.3-linux bll_and_function: gcc-2.95.3-linux constructor_tests: gcc-2.95.3-linux control_structures: gcc-2.95.3-linux exception_test: gcc-2.95.3-linux extending_rt_traits: gcc-2.95.3-linux is_instance_of_test: gcc-2.95.3-linux lambda_cast_test: gcc-2.95.3-linux operator_tests_simple: gcc-2.95.3-linux phoenix_control_structures: gcc-2.95.3-linux switch_construct: gcc-2.95.3-linux |logic| tribool_rename_test: gcc-2.95.3-linux tribool_test: gcc-2.95.3-linux |mpl| advance: gcc-2.95.3-linux always: gcc-2.95.3-linux apply: gcc-2.95.3-linux apply_wrap: gcc-2.95.3-linux arithmetic: gcc-2.95.3-linux assert: gcc-2.95.3-linux at: gcc-2.95.3-linux back: gcc-2.95.3-linux bind: gcc-2.95.3-linux bitwise: gcc-2.95.3-linux bool: gcc-2.95.3-linux comparison: gcc-2.95.3-linux contains: gcc-2.95.3-linux copy: gcc-2.95.3-linux copy_if: gcc-2.95.3-linux count: gcc-2.95.3-linux count_if: gcc-2.95.3-linux deque: gcc-2.95.3-linux distance: gcc-2.95.3-linux empty: gcc-2.95.3-linux equal: gcc-2.95.3-linux erase: gcc-2.95.3-linux erase_range: gcc-2.95.3-linux eval_if: gcc-2.95.3-linux filter_view: gcc-2.95.3-linux find: gcc-2.95.3-linux find_if: gcc-2.95.3-linux fold: gcc-2.95.3-linux for_each: gcc-2.95.3-linux front: gcc-2.95.3-linux identity: gcc-2.95.3-linux if: gcc-2.95.3-linux index_of: gcc-2.95.3-linux inherit: gcc-2.95.3-linux insert: gcc-2.95.3-linux insert_range: gcc-2.95.3-linux int: gcc-2.95.3-linux integral_c: gcc-2.95.3-linux is_placeholder: gcc-2.95.3-linux iterator_tags: gcc-2.95.3-linux joint_view: gcc-2.95.3-linux lambda: gcc-2.95.3-linux lambda_args: gcc-2.95.3-linux largest_int: gcc-2.95.3-linux list: gcc-2.95.3-linux list_c: gcc-2.95.3-linux logical: gcc-2.95.3-linux lower_bound: gcc-2.95.3-linux max_element: gcc-2.95.3-linux min_max: gcc-2.95.3-linux msvc_is_class: gcc-2.95.3-linux multiset: gcc-2.95.3-linux next: gcc-2.95.3-linux no_has_xxx: gcc-2.95.3-linux numeric_ops: gcc-2.95.3-linux pair_view: gcc-2.95.3-linux partition: gcc-2.95.3-linux pop_front: gcc-2.95.3-linux push_front: gcc-2.95.3-linux quote: gcc-2.95.3-linux range_c: gcc-2.95.3-linux remove: gcc-2.95.3-linux remove_if: gcc-2.95.3-linux replace: gcc-2.95.3-linux replace_if: gcc-2.95.3-linux reverse: gcc-2.95.3-linux same_as: gcc-2.95.3-linux single_view: gcc-2.95.3-linux size: gcc-2.95.3-linux size_t: gcc-2.95.3-linux gcc-4_0-darwin sizeof: gcc-2.95.3-linux sort: gcc-2.95.3-linux stable_partition: gcc-2.95.3-linux template_arity: gcc-2.95.3-linux transform: gcc-2.95.3-linux transform_view: gcc-2.95.3-linux unique: gcc-2.95.3-linux unpack_args: gcc-2.95.3-linux upper_bound: gcc-2.95.3-linux vector: gcc-2.95.3-linux vector_c: gcc-2.95.3-linux zip_view: gcc-2.95.3-linux |multi_array| access: gcc-2.95.3-linux idxgen1: gcc-2.95.3-linux index_bases: gcc-2.95.3-linux range1: gcc-2.95.3-linux reshape: gcc-2.95.3-linux slice: gcc-2.95.3-linux storage_order: gcc-2.95.3-linux |numeric/conversion| numeric_cast_test: gcc-2.95.3-linux udt_example_0: gcc-2.95.3-linux |numeric/interval| add: gcc-2.95.3-linux cmp: gcc-2.95.3-linux cmp_exp: gcc-2.95.3-linux det: gcc-2.95.3-linux fmod: gcc-2.95.3-linux integer: gcc-2.95.3-linux mul: gcc-2.95.3-linux overflow: gcc-2.95.3-linux pi: gcc-2.95.3-linux pow: gcc-2.95.3-linux test_float: gcc-2.95.3-linux |optional| optional_test: gcc-2.95.3-linux optional_test_inplace: gcc-2.95.3-linux optional_test_ref: gcc-2.95.3-linux optional_test_tie: gcc-2.95.3-linux |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc tutorial: gcc-2.95.3-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 unwrap_cv_reference: gcc-2.95.3-linux |property_map| dynamic_properties_test: gcc-2.95.3-linux property_map_cc: gcc-2.95.3-linux |python| andreas_beyer: gcc-2.95.3-linux back_reference: gcc-2.95.3-linux bases: gcc-2.95.3-linux ben_scott1: gcc-2.95.3-linux bienstman1: gcc-2.95.3-linux bienstman2: gcc-2.95.3-linux bienstman3: gcc-2.95.3-linux borrowed: gcc-2.95.3-linux builtin_converters: gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux vc-7_1 const_argument: gcc-2.95.3-linux copy_ctor_mutates_rhs: gcc-2.95.3-linux defaults: gcc-2.95.3-linux destroy_test: gcc-2.95.3-linux dict: gcc-2.95.3-linux docstring: gcc-2.95.3-linux exec: gcc-2.95.3-linux intel-win32-9_0 if_else: gcc-2.95.3-linux indirect_traits_test: gcc-2.95.3-linux injected: gcc-2.95.3-linux keywords: gcc-2.95.3-linux long: gcc-2.95.3-linux minimal: gcc-2.95.3-linux multi_arg_constructor: gcc-2.95.3-linux nested: gcc-2.95.3-linux numpy: gcc-2.95.3-linux object_manager: gcc-2.95.3-linux operators: gcc-2.95.3-linux pearu1: gcc-2.95.3-linux pickle1: gcc-2.95.3-linux pickle3: gcc-2.95.3-linux pickle4: gcc-2.95.3-linux pointee: gcc-2.95.3-linux pointer_type_id_test: gcc-2.95.3-linux pointer_vector: gcc-2.95.3-linux properties: gcc-2.95.3-linux raw_ctor: gcc-2.95.3-linux result: gcc-2.95.3-linux return_arg: gcc-2.95.3-linux select_arg_to_python_test: gcc-2.95.3-linux select_from_python_test: gcc-2.95.3-linux select_holder: gcc-2.95.3-linux staticmethod: gcc-2.95.3-linux str: gcc-2.95.3-linux string_literal: gcc-2.95.3-linux tuple: gcc-2.95.3-linux upcast: gcc-2.95.3-linux |random| random_demo: gcc-2.95.3-linux random_test: gcc-2.95.3-linux |rational| rational_example: gcc-2.95.3-linux |regex| bad_expression_test: gcc-2.95.3-linux captures_example: gcc-2.95.3-linux captures_test: gcc-2.95.3-linux collate_info: gcc-2.95.3-linux concept_check: gcc-2.95.3-linux credit_card_example: gcc-2.95.3-linux icu_concept_check: gcc-2.95.3-linux icu_example: gcc-2.95.3-linux mfc_example: gcc-2.95.3-linux object_cache_test: gcc-2.95.3-linux partial_regex_grep: gcc-2.95.3-linux partial_regex_match: gcc-2.95.3-linux posix_api_check: gcc-2.95.3-linux posix_api_check_cpp: gcc-2.95.3-linux recursion_test: gcc-2.95.3-linux regex_config_info: gcc-2.95.3-linux regex_dll_config_info: gcc-2.95.3-linux regex_grep_example_1: gcc-2.95.3-linux regex_grep_example_2: gcc-2.95.3-linux regex_grep_example_3: gcc-2.95.3-linux regex_grep_example_4: gcc-2.95.3-linux regex_iterator_example: gcc-2.95.3-linux regex_match_example: gcc-2.95.3-linux regex_merge_example: gcc-2.95.3-linux regex_regress: gcc-2.95.3-linux regex_regress_dll: gcc-2.95.3-linux regex_replace_example: gcc-2.95.3-linux regex_search_example: gcc-2.95.3-linux regex_split_example_1: gcc-2.95.3-linux regex_split_example_2: gcc-2.95.3-linux regex_timer: gcc-2.95.3-linux regex_token_iterator_eg_1: gcc-2.95.3-linux regex_token_iterator_eg_2: gcc-2.95.3-linux static_mutex_test: gcc-2.95.3-linux unicode_iterator_test: gcc-2.95.3-linux wide_posix_api_check_cpp: gcc-2.95.3-linux |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |signals| dead_slot_test: gcc-2.95.3-linux deletion_test: gcc-2.95.3-linux ordering_test: gcc-2.95.3-linux signal_n_test: gcc-2.95.3-linux signal_test: gcc-2.95.3-linux trackable_test: gcc-2.95.3-linux |smart_ptr| atomic_count_test: gcc-2.95.3-linux get_deleter_test: gcc-2.95.3-linux intrusive_ptr_test: gcc-2.95.3-linux lw_mutex_test: gcc-2.95.3-linux shared_from_this_test: gcc-2.95.3-linux shared_ptr_basic_test: gcc-2.95.3-linux shared_ptr_test: gcc-2.95.3-linux smart_ptr_test: gcc-2.95.3-linux weak_ptr_test: gcc-2.95.3-linux |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |static_assert| static_assert_example_2: gcc-2.95.3-linux static_assert_example_3: gcc-2.95.3-linux static_assert_test: gcc-2.95.3-linux |test| algorithms_test: gcc-2.95.3-linux auto_unit_test_test: gcc-2.95.3-linux auto_unit_test_test_mult: gcc-2.95.3-linux boost_check_equal_str: gcc-2.95.3-linux class_properties_test: gcc-2.95.3-linux custom_exception_test: gcc-2.95.3-linux errors_handling_test: gcc-2.95.3-linux fixed_mapping_test: gcc-2.95.3-linux foreach_test: gcc-2.95.3-linux ifstream_line_iterator_test: gcc-2.95.3-linux online_test: gcc-2.95.3-linux output_test_stream_test: gcc-2.95.3-linux parameterized_test_test: gcc-2.95.3-linux result_report_test: gcc-2.95.3-linux test_case_template_test: gcc-2.95.3-linux test_fp_comparisons: gcc-2.95.3-linux test_tools_test: gcc-2.95.3-linux |thread| test_barrier: gcc-2.95.3-linux test_barrier_lib: gcc-2.95.3-linux test_condition: gcc-2.95.3-linux gcc-3_4_3-sunos test_condition_lib: gcc-2.95.3-linux test_mutex: gcc-2.95.3-linux gcc-3_4_3-sunos test_mutex_lib: gcc-2.95.3-linux test_once: gcc-2.95.3-linux test_once_lib: gcc-2.95.3-linux test_read_write_mutex: gcc-2.95.3-linux test_read_write_mutex_lib: gcc-2.95.3-linux test_thread: gcc-2.95.3-linux test_thread_lib: gcc-2.95.3-linux test_tss: gcc-2.95.3-linux gcc-3_4_3-sunos gcc-3_4_3-sunos test_tss_lib: gcc-2.95.3-linux test_xtime: gcc-2.95.3-linux test_xtime_lib: gcc-2.95.3-linux |timer| timer_test: gcc-2.95.3-linux |tokenizer| examples: gcc-2.95.3-linux simple_example_1: gcc-2.95.3-linux simple_example_2: gcc-2.95.3-linux simple_example_3: gcc-2.95.3-linux simple_example_4: gcc-2.95.3-linux simple_example_5: gcc-2.95.3-linux |tuple| io_test: gcc-2.95.3-linux tuple_test_bench: gcc-2.95.3-linux gcc-3_4_3-sunos |type_traits| add_const_test: gcc-2.95.3-linux add_cv_test: gcc-2.95.3-linux add_pointer_test: gcc-2.95.3-linux add_reference_test: gcc-2.95.3-linux add_volatile_test: gcc-2.95.3-linux aligned_storage_test: gcc-2.95.3-linux alignment_of_test: gcc-2.95.3-linux decay_test: gcc-2.95.3-linux extent_test: gcc-2.95.3-linux function_traits_test: gcc-2.95.3-linux has_nothrow_assign_test: gcc-2.95.3-linux has_nothrow_constr_test: gcc-2.95.3-linux has_nothrow_copy_test: gcc-2.95.3-linux has_trivial_assign_test: gcc-2.95.3-linux has_trivial_constr_test: gcc-2.95.3-linux has_trivial_copy_test: gcc-2.95.3-linux has_trivial_destructor_test: gcc-2.95.3-linux has_virtual_destructor_test: gcc-2.95.3-linux is_arithmetic_test: gcc-2.95.3-linux is_array_test: gcc-2.95.3-linux is_base_and_derived_test: gcc-2.95.3-linux is_base_of_test: gcc-2.95.3-linux is_class_test: gcc-2.95.3-linux is_compound_test: gcc-2.95.3-linux is_const_test: gcc-2.95.3-linux is_empty_test: gcc-2.95.3-linux is_enum_test: gcc-2.95.3-linux is_float_test: gcc-2.95.3-linux is_floating_point_test: gcc-2.95.3-linux is_function_test: gcc-2.95.3-linux is_fundamental_test: gcc-2.95.3-linux is_integral_test: gcc-2.95.3-linux is_member_func_test: gcc-2.95.3-linux is_member_obj_test: gcc-2.95.3-linux is_member_pointer_test: gcc-2.95.3-linux is_object_test: gcc-2.95.3-linux is_pod_test: gcc-2.95.3-linux is_pointer_test: gcc-2.95.3-linux is_polymorphic_test: gcc-2.95.3-linux is_reference_test: gcc-2.95.3-linux is_same_test: gcc-2.95.3-linux is_scalar_test: gcc-2.95.3-linux is_signed_test: gcc-2.95.3-linux is_stateless_test: gcc-2.95.3-linux is_union_test: gcc-2.95.3-linux is_unsigned_test: gcc-2.95.3-linux is_void_test: gcc-2.95.3-linux is_volatile_test: gcc-2.95.3-linux rank_test: gcc-2.95.3-linux remove_all_extents_test: gcc-2.95.3-linux remove_bounds_test: gcc-2.95.3-linux remove_const_test: gcc-2.95.3-linux remove_cv_test: gcc-2.95.3-linux remove_extent_test: gcc-2.95.3-linux remove_pointer_test: gcc-2.95.3-linux remove_reference_test: gcc-2.95.3-linux remove_volatile_test: gcc-2.95.3-linux tricky_abstract_type_test: gcc-2.95.3-linux intel-win32-9_0 tricky_add_pointer_test: gcc-2.95.3-linux tricky_incomplete_type_test: gcc-2.95.3-linux tricky_partial_spec_test: gcc-2.95.3-linux type_with_alignment_test: gcc-2.95.3-linux udt_specialisations: gcc-2.95.3-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |utility| addressof_test: gcc-2.95.3-linux assert_test: gcc-2.95.3-linux base_from_member_test: gcc-2.95.3-linux binary_search_test: gcc-2.95.3-linux call_traits_test: gcc-2.95.3-linux compressed_pair_test: gcc-2.95.3-linux current_function_test: gcc-2.95.3-linux iterators_test: gcc-2.95.3-linux next_prior_test: gcc-2.95.3-linux numeric_traits_test: gcc-2.95.3-linux operators_test: gcc-2.95.3-linux ref_ct_test: gcc-2.95.3-linux ref_test: gcc-2.95.3-linux shared_iterator_test: gcc-2.95.3-linux value_init_test: gcc-2.95.3-linux |variant| recursive_variant_test: gcc-2.95.3-linux variant_comparison_test: gcc-2.95.3-linux variant_reference_test: gcc-2.95.3-linux variant_test1: gcc-2.95.3-linux variant_test2: gcc-2.95.3-linux variant_test3: gcc-2.95.3-linux variant_test4: gcc-2.95.3-linux variant_test5: gcc-2.95.3-linux variant_test6: gcc-2.95.3-linux variant_test7: gcc-2.95.3-linux variant_test8: gcc-2.95.3-linux variant_visit_test: gcc-2.95.3-linux |xpressive| test3: gcc-3.4.4-linux test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5: gcc-3.4.4-linux test5u: gcc-3_3-darwin test6: gcc-3.4.4-linux test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

Re: [boost] [Review] of binary_int utility starts
by Scott Schurr 17 Oct '05

17 Oct '05

Markus Sch?pflin <markus.schoepflin(a)comsoft.de> wrote: > Compiles and works now without any warnings or errors. Great. And thanks for trying it. > For the next test, I changed struct test_values (in binary_int_test.cpp) to > the following: > > struct test_values { > uint64_t hex_value; > uint64_t bin_value; > }; > > This additionally needs #include <boost/cstdint.hpp>. > > When compiling and running this (on both 32 bit and 64 bit systems), I got > the following error: > > At test_array index 40 8a6c4e20 != ffffffff8a6c4e20 > assertion "test_array[i].hex_value == test_array[i].bin_value" failed: file > "../binary_int_test.cpp", line 118 Thanks for trying this. I've seen errors like this that were removed by changing all of the literals in the file to unsigned by appending a 'u'. I suspect that there's a problem with the size of the literals on the 64-bit compilers. Does one declare a 64-bit literal by appending a double L ('LL')? If so, then I'll give that a try. Thanks. Scott Schurr

2 1

Re: [boost] [Review] of binary_int utility starts
by Scott Schurr 17 Oct '05

17 Oct '05

Markus Sch?pflin <markus.schoepflin(a)comsoft.de> wrote: > Tried on Tru64 5.1, CXX 7.1-006: > > > cxx -model ansi -std strict_ansi -I boost-HEAD binary_int_test.cpp > > cxx: Error: binary_int.hpp, line 51: incomplete type is not allowed > binary_nibble_VALID_VALUES_BINARY_0000_THROUGH_1111<false> t; > ---------------------------------------------------------------^ > cxx: Warning: binary_int.hpp, line 101: trailing comma is nonstandard > shl = 4u, > ------------------^ > cxx: Warning: binary_int.hpp, line 109: trailing comma is nonstandard > shl = 0u, > ------------------^ > cxx: Warning: binary_int.hpp, line 191: trailing comma is nonstandard > v0_ = (v1_ << binary_int_arg<b0>::shl) | binary_int_arg<b0>::value, > -----------------------------------------------------------------------------^ > cxx: Warning: binary_int.hpp, line 171: missing return statement at end of > non-void function "binary_int<b15, b14, b13, b12, b11, b10, b9, b8, > b7, b6, b5, b4, b3, b2, b1, b0>::operator=" > binary_int& operator=(const binary_int& rhs) { }; > ---------------------------------------------------^ > cxx: Info: 1 error detected in the compilation of "binary_int_test.cpp". I have attempted fixes for these errors. 1. I removed the BOOST_WORKAROUND, and made what was the BOOST_WORKAROUND the only behavior. 2. I removed trailing commas at the end of three enum definitions. 3. I removed the assignment operator definition from the protected section. I am hoping that with these changes the template will survive appropriately picky compilers with no warnings or errors. Unfortunately I can't verify my changes because my compilers are passing both the old and new versions of the template. I have uploaded the new version of the zip to the sandbox: http://boost-consulting.com/vault/ under the name binary_int. I hope that I actually improved the template :-). I'm sure I'll hear. Thanks. And thanks for your efforts on the review. Scott Schurr

2 1

[quickbook] chapters and sections
by Joel de Guzman 17 Oct '05

17 Oct '05

Hi, I just realized that quickbook does not have chapters! Looking at the boostbook.xml output, I see many chapters. In quickbook, a whole qbk is regarded as one whole chapter. I was wondering why we were generating a 2 level deep hierarchy of html pages. Deeper than that, the sub- sections are placed within it's parent section's html page. With chapters, we have more structure. Fortunately, this is easy to fix. I can easily add a [chapter title], [endchapter] markup built on top of the section mechanism. Actually, I can even do this without necessitating syntax change by simply assuming the outermost [section] as chapters. Your thoughts? Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net

2 2

[Signals] Fixed shared library issues on RC_1_33_0
by Douglas Gregor 16 Oct '05

16 Oct '05

I've just checked in a fix for the shared library/symbol visibility problems with Signals. If you've had problems with this before, please test! It's on the RC_1_33_0 branch for the 1.33.1 beta release. Doug

3 4

select_stdlib_config.hpp patch breaks gcc 2.96 build (Redhat 7.3)
by Ralf W. Grosse-Kunstleve 16 Oct '05

16 Oct '05

The select_stdlib_config.hpp patch below from 10/15/2005 breaks our Redhat 7.3 build of Boost.Python. An example error message is also shown below. Could this be fixed with BOOST_NO_LIMITS guards or something similar? Thanks! Cheers, Ralf % cvs -q diff -r1.11 -r1.12 select_stdlib_config.hpp Index: select_stdlib_config.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/config/select_stdlib_config.hpp,v retrieving revision 1.11 retrieving revision 1.12 diff -r1.11 -r1.12 15c15 < // library is in use, use <iosfwd> as it's about the smallest --- > // library is in use, use <iosfwd> and <limits> as they're about the smallest 18a19,22 > // PLEASE NOTE that the config system must not include any of the headers > // that are modified by TR1 (<memory>, <functional> or <utility>) not even > // indirectly. If they do so then the Boost TR1 implementation will be unusable. > // 20a25 > #include <limits> In file included from /net/taipan/scratch1/rwgk/auto_build/sources/boost/boost/config.hpp:40, from /net/taipan/scratch1/rwgk/auto_build/sources/boost/boost/python/detail/config.hpp:15, from /net/taipan/scratch1/rwgk/auto_build/sources/boost/boost/python/detail/prefix.hpp:14, from /net/taipan/scratch1/rwgk/auto_build/sources/boost/boost/python/handle.hpp:8, from /net/taipan/scratch1/rwgk/auto_build/sources/boost/boost/python/converter/arg_to_python_base.hpp:7, from /net/taipan/scratch1/rwgk/auto_build/sources/boost/libs/python/src/converter/arg_to_python_base.cpp:6: /net/taipan/scratch1/rwgk/auto_build/sources/boost/boost/config/select_stdlib_config.hpp:25:18: limits: No such file or directory __________________________________ Yahoo! Music Unlimited Access over 1 million songs. Try it free. http://music.yahoo.com/unlimited/

2 1

[1.33.1] [Thread] read_write_mutex
by Douglas Gregor 16 Oct '05

16 Oct '05

A while back, John Maddock pointed out that we have serious problems with read_write_mutex: http://lists.boost.org/Archives/boost/2005/09/93180.php Have we addressed these problems to everyone's satisfaction? If so, great; if not, we need to remove read_write_mutex from the RC_1_33_0 branch immediately. Doug

3 3

[Bug][Tools] Incomplete tool documentation, especially for building
by Daryle Walker 16 Oct '05

16 Oct '05

[This is for the versions at <http://www.boost.org>.] [I don't know if this should/could be placed in the Bug Tracker.] While answering a post about BCP on another list, I noticed that the docs for BCP (at <http://www.boost.org/tools/bcp/bcp.html>) never actually say where one would get BCP from! Looking at my local archive, I see the BCP source files are in the same directory as the BCP doc file. I noticed that they are C++ code; I suspected that BCP could have been a (Python) script or (if I didn't respond to a question asking why not) pre-made executables. I feel that the BCP docs should explain how to get BCP. In fact the QuickBook and Wave tools have the same problem. (The source for both is C++-based and in different subdirectories in the "tools" directory, but the docs never tell you that!) The other tools (build, regression, inspect, and BoostBook) do have building directions, but they're either indirectly linked or plainly presented. QuickBook has another problem in that it has no table of contents. I thought the docs were severely incomplete until I finally saw the little right arrow symbols at the two right-side corners. Nor did I know how big the QB docs were until I had to traverse every page through a chain of right arrow links. The Wave-tool docs have a different additional problem in that it's mixed in the Wave-library docs. The traversal symbols on that page shouldn't be followed since they can't help with the tool (just with Wave-library). The page isn't next to the Wave-tool source code, either. -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

5 4

[config] <iosfwd> and g++ 2.95
by Daniel James 16 Oct '05

16 Oct '05

select_stdlib_config.hpp has just been changed to include <iosfwd> instead of <utility>. But g++ 2.95's standard library has its own iostreams implementation which doesn't define __STL_CONFIG_H. It does define __IOSFWD__, so maybe that could be checked for as well? Is it okay to commit the attached patch? I've changed sgi.hpp to go back to including <utility> if __STL_CONFIG_H isn't defined so that anything that checks for _STL_CONFIG_H will still work. Also, if __IOSFWD__ happens to be used in another library, it will fail to compile. Daniel

2 5

concurrent_hash_map, RFC
by Peter Dimov 16 Oct '05

16 Oct '05

A preliminary documentation for a concurrent_hash_map is available: http://www.pdimov.com/cpp/concurrent_hash_map.html There exists a prototype implementation for that :-) and I'll post it online after a bit of cleanup. I have a question on the interface that hopefully may be of interest to someone. concurrent_hash_map implements the following member function: template<class F> bool find_and_visit( K const & k, F f ); that looks up the element with a key k in the map and, if found, invokes f on its associated value. This can be useful in a number of situations, but it poses the following problem: what if two threads call find_and_visit at the same time with the same k and f modifies its argument? Should the map serialize the two calls to f, or should it leave the responsibility of ensuring proper synchronization (or atomic update, if the mapped_type allows it) to the user? Thanks in advance for any comments/opinions on the interface. -- Peter Dimov http://www.pdimov.com

2 2

Boost Birds of Feather @ OOPSLA 05? (try 2)
by Jeff Garland 15 Oct '05

15 Oct '05

All - I'm going to be in San Diego @ OOPSLA next week and I'm wondering if any Boost users and developers would be interested in getting together for a BOF one evening. Obvious topic of discussion is all things Boost/C++/TR2. Right now I'm thinking Tuesday night would be a good time. Let me know if there is interest and I'll set this up. Jeff Note, I cross-posted to the user and developer list b/c the idea is this would be open to everyone with an interest in Boost.

1 0

Boost Birds of Feather @ OOPSLA 05?
by Jeff Garland 15 Oct '05

15 Oct '05

All - I'm going to be in San Diego @ OOPSLA next week and I'm wondering if any Boost users and developers would be interested in getting together for a BOF one evening. Obvious topic of discussion is all things Boost/C++/TR2. Right now I'm thinking Tuesday night would be a good time. Let me know if there is interest and I'll set this up. Jeff Note, I cross-posted to the user and developer list b/c the idea is this would be open to everyone with an interest in Boost.

1 0

Where do we get dark magic, evil-looking sacrificial knives and virgins?[1]
by Andreas Pokorny 15 Oct '05

15 Oct '05

Hi, Some weeks ago someone metioned that we need a C++ variant of CPAN or CTAN. The idea is really great. But I have no clue where we would start. How should that service look like, and work internally? I think we need some identifcation service for authors, maybe some access control on the packages stored in the serivce. The client frontend will need something to select mirrors, track dependencies to other packages. An auto build, intstall and test feature would be nice too. As Martin Wille just mentioned, something with some of these features already exists. Gentoos portage [2], written in python handles, dependencies, integrates a mirror selector, automatically build installs and uinstalls packages fetched as source code. The package scripts are shared using rsync[3]. The package source files are automatically distributed into their mirror system. The only missing thing is the author identification and access control part. Gentoo "works" with an indirect system, requiring authors to provide scripts, or users to beg for packages in their bugzilla system. Another interesting system could be provided by monotone[4], a very nice distributed version control system. We could use monotone to replace rsync, in the suggestion above. Monotone provides a secure system to get the build scripts anonymously, and allows identifying authors. The distributive character of monotone allows very intersting use cases, in which authors are able to update and provide new versions of their software. [1] http://www.cpan.org/misc/cpan-faq.html#How_does_the_CPAN_work [2] http://www.gentoo.org/main/en/about.xml [3] http://samba.anu.edu.au/rsync/ [4] http://venge.net/monotone/ Regards Andreas Pokorny

3 2

[Serialization] why operator &()?
by Jim Hyslop 15 Oct '05

15 Oct '05

I've been looking at the serialization library (nice work, Robert) and I have a question. I searched the archives and didn't see any discussion on this, and I'm sorry I missed all the pre-approval discussion, or I would have said something sooner. What is the rationale behind using 'operator &()' to mean 'serialize this item?' I find a statement like 'ar & member1;' to be very non-intuitive: how does bitwise-and relate to serialization? It seems to me that most sensible code guidelines admonish against this kind of operator abuse (pardon my bluntness, but that's what it is when you get down to it). -- Jim

7 13

Re: [boost] [ANN] Phoenix-2 prerelease
by Lucas Galfaso 15 Oct '05

15 Oct '05

typo? The "Algorithm" page reads: find_end(r1, r2[, f]) find_end(begin(r1), end(r1), begin(r2), end(r2)[, f]) is this right? (look at the extra [ ] ) Anyhow, impresive work!!!! LG "Joel de Guzman" <joel(a)boost-consulting.com> wrote in message news:dijjbq$9uf$1@sea.gmane.org... > Hi, > > Here's a pre-release package of Phoenix-2. Jaakko and I agreed > that it will be the basis of the Phoenix and Boost Lambda > merger. This version is Phoenix 1 + Lambda + a lot more. > > Take note though that this is not a drop-in replacement of > Phoenix-1 for Spirit users. In particular, there is no > closure support. Phoenix-2 has true local variables. The > plan for Spirit-2 is to replace closures with local variables. > > Docs: http://tinyurl.com/77pz5 > > The pre-release package is here: > http://spirit.sourceforge.net/dl_more/phoenix_v2.zip > > Just drop it where Phoenix-1 is and run the examples/tests. > Comments, feedback very welcome! > > Cheers, > -- > Joel de Guzman > http://www.boost-consulting.com > http://spirit.sf.net > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl

1 1

Macros at namespace scope: trailing semicolon?
by David Abrahams 14 Oct '05

14 Oct '05

I am defining a macro, BOOST_PARAMETER_KEYWORD(tag_namespace, name) that declares a keyword for the Parameter library. It has to be used at namespace scope. I have the option to define it so that correct usage requires a trailing semicolon, or so that the trailing semicolon is forbidden. Unfortunately I don't have the ability to make it optional. Which should I choose? IMO there's no chance of confusing it with a function call, since a function call would be illegal in the context in which it's used, and people are naturally more likely to add a semicolon without thinking about it, and if I design the macro so that a semicolon is required it will interact more smoothly with editors and pretty-printers. So I can't see any good reason not to require the semicolon. Arguments? -- Dave Abrahams Boost Consulting www.boost-consulting.com

19 87

[wave] Using wave to preprocess boost headers
by Thomas Andersen 14 Oct '05

14 Oct '05

I have tried to get wave to preprocess the boost headers. However I get an error in cstdint.hpp line 246 # if ULONG_MAX == 18446744073709551615 // 2**64 - 1 error: ill formed integer literal or integer constant too large: 18446744073709551615 Have anybody else encountered this problem, and found a way around it? Best regards, Thomas Andersen

4 4

Boost regression notification (2005-10-14 [RC_1_33_0])
by Douglas Gregor 14 Oct '05

14 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-14T13:51:13Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 76 failures in 5 libraries: parameter (3) python (2) range (3) serialization (63) variant (5) |parameter| tutorial: borland-5_6_4 gcc-2.95.3-linux unnamed: vc-7_1 |python| pointer_vector: cw-9_4 vector_indexing_suite: cw-9_4 |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_exported_binary_archive: vc-6_5 test_exported_binary_archive_dll: vc-6_5 test_exported_text_archive: vc-6_5 test_exported_text_archive_dll: vc-6_5 test_exported_text_warchive: vc-6_5 test_exported_text_warchive_dll: vc-6_5 test_exported_xml_archive: vc-6_5 test_exported_xml_archive_dll: vc-6_5 test_exported_xml_warchive: vc-6_5 test_exported_xml_warchive_dll: vc-6_5 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: intel-win32-8_1 vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 |variant| recursive_variant_test: mingw-3_4_2 variant_test4: mingw-3_4_2 variant_test6: mingw-3_4_2 variant_test7: mingw-3_4_2 variant_test8: mingw-3_4_2

1 0

Boost regression notification (2005-10-14 [HEAD])
by Douglas Gregor 14 Oct '05

14 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-14T05:00:23Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 141 failures in 12 libraries: concept_check (13) graph (2) mpl (1) parameter (14) python (1) serialization (36) spirit (8) thread (4) tuple (1) type_traits (1) typeof (21) xpressive (39) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc tutorial: gcc-2.95.3-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |python| exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| tricky_abstract_type_test: intel-win32-9_0 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test1: intel-win32-9_0 test1u: intel-win32-9_0 test2: gcc-3.3.6-linux gcc-3_3-darwin intel-win32-9_0 test2u: gcc-3.3.6-linux gcc-3_3-darwin intel-win32-9_0 test3: gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 test3u: gcc-3.3.6-linux gcc-3_3-darwin intel-win32-9_0 test4: gcc-3.3.6-linux gcc-3_3-darwin test4u: gcc-3.3.6-linux gcc-3_3-darwin test5: gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin test5u: gcc-3.3.6-linux gcc-3_3-darwin test6: gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin test6u: gcc-3.3.6-linux gcc-3_3-darwin test7: intel-win32-9_0 test7u: intel-win32-9_0 test8: intel-win32-9_0 test8u: intel-win32-9_0 test9: gcc-3.3.6-linux gcc-3_3-darwin intel-win32-9_0 test9u: gcc-3.3.6-linux gcc-3_3-darwin intel-win32-9_0

1 0

Re: [boost] Interest in dimension/unit-checking library?
by Scott Schurr 14 Oct '05

14 Oct '05

I'm no where close to the expert that you guys are, so I'll quickly toss in my two cents and get out of your way. On 10/13/05 Matt Calabrese <rivorus(a)gmail.com> wrote: > > On 10/13/05, Deane Yang <deane_yang(a)yahoo.com> wrote: > > > > Mathematically, I think Andy is entirely correct in what he says above. > > Once you take the ratio of two measurements of the same dimension (or > > quantity), you end up with a pure number that really can't be > > distinguished from other ratios or pure numbers. > > > I tend to disagree here. A ratio of two lengths, for example, is in > fact a value in radians. Um, careful there. Suppose I'm measuring the height of a shrub at various points in time. If I take one of those measurements and divide it by a measurement taken at a different time, then I get a ratio that expresses the shrub's change in height in a unitless way - I get the same value whether I made my measurements in meters, inches, or furlongs. This is an example of a common case where dividing two lengths doesn't give radians - it's just a ratio. The dimension/unit-checking library should solve the problems that it has enough information to solve. When it runs out of information it should ask for help. Would it make sense to have something like a unitless_cast<radians>? Scott Schurr

6 5

[graph][1.33.1] STLport 5 compile problems.
by Rene Rivera 14 Oct '05

14 Oct '05

There seems to be a conflict between the Graph library and the new STLport... http://tinyurl.com/dk2fc [1] [1] http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/o… -- -- 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

2 4

[Boost-bugs] [ boost-Feature Requests-1326829 ] STLPort with NO_IOSTREAMS
by SourceForge.net 14 Oct '05

14 Oct '05

Feature Requests item #1326829, was opened at 2005-10-14 16:38 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=1326829&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: NN (nn1234) Assigned to: Nobody/Anonymous (nobody) Summary: STLPort with NO_IOSTREAMS Initial Comment: Boost does specializations for streams even when _STLP_NO_IOSTREAMS defined. It would be nice to not specialize classes with streams when _STLP_NO_IOSTREAMS macro is defined. Thanx. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1326829&group_… ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

VC++ 7.1 build options lead to AV
by Ashok Thirumurthi 14 Oct '05

14 Oct '05

Dear Boost, The following call stack leads to an access violation when I link a VC 7.1 DLL to the release build of the boost signals 1_33_0 DLL. In comparison, there is no access violation when I link to the debug build of the same library. Similarly, when I add the signals source to my own release DLL, there is no access violation. I attempted to disable all compiler optimizations in msvc.jam as follows. However, after running bjam -a in signals\build and installing the output, the AV still occurs. # 8.0 deprecates some of the options if ! [ MATCH ^([67].*) : $(version) ] { # flags msvc.compile CFLAGS $(condition)/<optimization>speed : /O2 ; # flags msvc.compile CFLAGS $(condition)/<optimization>space : /O1 ; flags msvc.link.dll MANIFEST : "mt -manifest " ; flags msvc.link.dll OUTPUTRESOURCE : "-outputresource:" ; } else { # flags msvc.compile CFLAGS $(condition)/<optimization>speed : /Ogity /O2 /Gs ; # flags msvc.compile CFLAGS $(condition)/<optimization>space : /Ogisy /O1 /Gs ; } Note that I have a default installation of Visual Studio 2003. How can I alter the release build to avoid the access violation? More information: Access violation reading location 0x00000004 (*((k2).content)).__vfptr is 0x00000000 bool operator()(const any& k1, const any& k2) const { if (k1.type() == typeid(front_type)) return !(k2.type() == typeid(front_type)); if (k1.type() == typeid(back_type)) return false; > if (k2.type() == typeid(front_type)) return false; if (k2.type() == typeid(back_type)) return true; > Colorado.dll!boost::signals::detail::any_bridge_compare<std::less<int>,int>::operator()(const boost::any & k1={...}, const boost::any & k2={...}) Line 54 + 0xc C++ Colorado.dll!boost::detail::function::function_obj_invoker2<boost::signals::detail::any_bridge_compare<std::less<int>,int>,bool,boost::any,boost::any>::invoke(boost::detail::function::any_pointer function_obj_ptr={...}, boost::any a0={...}, boost::any a1={...}) Line 119 + 0x1b C++ boost_signals-vc71-mt-1_33.dll!010a2340() boost_signals-vc71-mt-1_33.dll!010a2c6a() boost_signals-vc71-mt-1_33.dll!010a42be() boost_signals-vc71-mt-1_33.dll!010a4bd0() boost_signals-vc71-mt-1_33.dll!010a4dfc() boost_signals-vc71-mt-1_33.dll!010a5933() Colorado.dll!boost::signal0<bool,boost::last_value<bool>,int,std::less<int>,boost::function<bool __stdcall(void),std::allocator<void> > >::signal0<bool,boost::last_value<bool>,int,std::less<int>,boost::function<bool __stdcall(void),std::allocator<void> > >(const boost::last_value<bool> & c={...}, const std::less<int> & comp={...}) Line 198 + 0x85 C++ ... Do these observations suggest how I might successfully handle this callback from the release boost DLL? Thanks in advance, - Ashok Thirumurthi

1 0

Re: [boost] [ANN] Phoenix-2 prerelease
by Eric Niebler 14 Oct '05

14 Oct '05

Joel de Guzman wrote: > Docs: http://tinyurl.com/77pz5 > In "Block Statement", (http://tinyurl.com/b25hr) you show how to use the comma operator to sequence statements. I see problems here, especially when calling a function that takes a predicate that isn't the last argument. For instance, how would you use Phoenix to create a filter_iterator? iterator begin, end; ... boost::make_filter_iterator(arg1 > 5, begin, end); // Oops! ---------------------------^ Isn't that comma going to be Phoenix's overloaded comma? -- Eric Niebler Boost Consulting www.boost-consulting.com

3 3

Rephrase "Broken Compiler Workarounds"?
by Daryle Walker 14 Oct '05

14 Oct '05

I was just looking at the phrase "Broken Compiler Workarounds" on a page about Boost on Wikipedia <http://en.wikipedia.org/wiki/Boost_library>. I realized that a naïve look makes it ambiguous whether the compiler is broken or the workarounds are broken. Maybe a hyphen could go between the first two words? -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

4 3

Boost regression notification (2005-10-13 [RC_1_33_0])
by Douglas Gregor 14 Oct '05

14 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-13T14:34:13Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 75 failures in 6 libraries: graph (4) parameter (2) python (2) range (3) serialization (63) variant (1) |graph| copy: mingw-3_4_2 graph_concepts: mingw-3_4_2 graphviz_test: cw-9_4 vector_graph_cc: mingw-3_4_2 |parameter| tutorial: gcc-2.95.3-linux unnamed: vc-7_1 |python| pointer_vector: cw-9_4 vector_indexing_suite: cw-9_4 |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_exported_binary_archive: vc-6_5 test_exported_binary_archive_dll: vc-6_5 test_exported_text_archive: vc-6_5 test_exported_text_archive_dll: vc-6_5 test_exported_text_warchive: vc-6_5 test_exported_text_warchive_dll: vc-6_5 test_exported_xml_archive: vc-6_5 test_exported_xml_archive_dll: vc-6_5 test_exported_xml_warchive: vc-6_5 test_exported_xml_warchive_dll: vc-6_5 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: intel-win32-8_1 vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 |variant| variant_reference_test: mingw-3_4_2

6 7