- Boost - lists.boost.org

Re:Re: [boost] Regression Tests, Boost.Serialization
by Robert Ramey 16 Jul '04

16 Jul '04

>It might also be beneficial to allow finer grained results within a test >file. Let's say I have a test file stl_containers.cpp that tests >std::vector, std::list, etc. Now, if a compiler has a problem with one of >these (e.g. std::map) - if I understand the regression test system >correctly - it will mark this test as failed in the regression results and > a user >would assume that all the stl_containers would be unusable! That's the way it is now. That's why there are so many (too many) tests. About 20 tests for base services, void_cast, iterators, iteratorbase64, demo, etc. About 35 test for serialization facilities e.g. tracking, exporting, registering, stl::list, stl::vector, etc. These later are built/run for each archive type xml, wide xml, text, wide text and native binary. So this works out to about 20 + 35 * 5 = 190 (actually 209) * 5 compilers about 1000 test run/builds. Robert Ramey

1 0

Re:Re: [boost] Re: Serialization Menu
by Robert Ramey 16 Jul '04

16 Jul '04

>Robert Ramey wrote: >> I've just modified contents.html slightly so that the expand/collapse >> functionality is only enabled all of the following are true: >> >> a) scripting is supported by the browser >> b) scripting is not turned off >> c) the browser is either IE or Netscape >Please don't. As I've said, Konqueror has no problems whatsoever with your >JavaScript. Can't you make just special case for IE, and and single code >path for all other browsers? My concern was to address the issue raised by those such as yourself who felt that the javescript should be removed to be sure that its will work in all browsers. I feel this addresses that concern but still permits browsers on which the scripting has been test to use the collapse/expand functionality. What I have now is special case for IE and Netscape and no javascript for all other browsers. As far as I can tell, this should work for all browsers that support frames. If you've verified that Konqueror works well with the javascript then add it to the list in the javascript code. Then we can still have what we want and still maintain guaranteed compatibility on all browsers. Robert Ramey

1 0

RE: [boost] [config] _WIN32 question
by Ferdinand Prantl 16 Jul '04

16 Jul '04

Hi Volodya, > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of Vladimir Prus [snip] > > Borland: __WIN32__ _WIN32 > > Digital Mars: _WIN32 > > GCC (MinG/W and Cygwin with -mno-cygwin): __MINGW32__ WIN32 _WIN32 > > __WIN32 __WIN32__ > > Metrowerks: _WIN32 > > Microsoft: _WIN32 > > It seems that _WIN32 is defined by all of them.... Yep, _WIN32 is enough from the hard-wired switches to be sure about the Win32 platform, at least for what have done all the time. I forgot Watcom, which defines _WIN32 __WINDOWS_386__ :-) but they have still a long way to compile boost.org... > > The macro WIN32 is meant to be a user-definable option how > to enforce > > a WIN32 code if a compiler does not define _WIN32. > > Ok. When is it needed, BTW? Well, you have caught me. Actually, I did not need to use it yet. I have it in my configuration just to be flexible waiting for such code or compiler... AFAIK, MSVS from some interesting reasons keeps to generate new wizards-made projects and makefiles with the macro WIN32, dunno why. They may have some old sources with both #ifdef _WIN32 #endif and #ifdef WIN32 #endif and it does not pay off to them to correct it, I do not know. I use -DWIN32 as well in my makefiles and PLATFORM_WIN32 = _WIN32 || WIN32 in headers even if _WIN32 alone should be always enough. > > And if you like, it is possible to do something like this > to be complete: > > > > BOOST_WIN32 : _WIN32 || WIN32 > > BOOST_WIN64 : _WIN64| WIN64 > > BOOST_WINDOWS : BOOST_WIN32 || BOOST_WIN64 > > Yea, I think this makes sense. Though _WIN64 is not used > anywhere in config yet. It will start shortly, as soon as someone with a fresh new x86-64 from AMD starts to play with the boost::filesystem :-) Today one should be careful with BOOST_WINDOWS and check the 64-bit compatibility, if the macro will mark general Windows platform. Ferda > - Volodya

1 0

RE: [boost] lexical_cast reviewed
by Michiel Salters 16 Jul '04

16 Jul '04

> -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org]On Behalf Of Jason > Sent: vrijdag 16 juli 2004 11:03 > To: boost(a)lists.boost.org > Subject: [boost] lexical_cast reviewed > > SOURCE CODE: > #include <sstream> > using namespace std; > class lexical_cast { > public: > template <typename Source> lexical_cast( const Source & source ) { > ss << source; > } > > template <typename Target> operator Target() { > Target target; > ss >> target; > return target; > } > private: > stringstream ss; > }; Not really lexical_cast, but useful nevertheless. Perhaps we could call it lexical_auto_cast. It could be more efficient to store a string instead, but I'm not sure. Regards, Michiel Salters This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

2 1

[1.32 release] Branch for release postponed -- Plea for help
by Aleksey Gurtovoy 16 Jul '04

16 Jul '04

Branch for release scheduled for today, July 16, will NOT be performed. The two main showstoppers are an unsatisfactory state of the main trunk (http://tinyurl.com/25ar3) and a further delayed MPL check-in. It's going to take at least a couple more days for me to deal with the latter, and it would be really appreciated if during that time somebody would volunteer to work on clearing up the regression picture; the more volunteers, the better! Many library maintainers are already doing a good job at it, but the previous experience shows that whole thing can be made significantly more efficient if people who have local access to particular compilers failing on particular libraries [of their interest] took a look at those failures and reported back the results of their finding/posted patches/ checked in fixes. If each of us with a little bit of familiarity with the codebase/free time on their hands would take care of only a single failure, it would already make an enormous difference. Needless to say, everyone who contributes to this is going to be acknowledged when the release is out. (And a warm "thank you" to everybody who is already investing their time and energy into this!) -- Aleksey Gurtovoy MetaCommunications Engineering

4 4

Optional patch
by Hugo Duncan 16 Jul '04

16 Jul '04

The following clears the unexpected failure for optional on borland-5.6.4 Index: optional.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/optional/optional.hpp,v retrieving revision 1.1 diff -w -u -r1.1 optional.hpp --- optional.hpp 7 Jul 2004 15:10:03 -0000 1.1 +++ optional.hpp 16 Jul 2004 13:11:36 -0000 @@ -347,7 +347,7 @@ reference_const_type dereference( internal_type const* p, is_reference_tag ) const { return p->get() ; } reference_type dereference( internal_type* p, is_reference_tag ) { return p->get() ; } - void destroy_impl ( is_not_reference_tag ) { get_ptr_impl()->T::~T() ; m_initialized = false ; } + void destroy_impl ( is_not_reference_tag ) { get_ptr_impl()->internal_type::~internal_type() ; m_initialized = false ; } void destroy_impl ( is_reference_tag ) { m_initialized = false ; } // If T is of reference type, trying to get a pointer to the held value must result in a compile-time error.

2 1

[multi_array] problems with metacomm reports?
by Joaquín Mª López Muñoz 16 Jul '04

16 Jul '04

Please see http://tinyurl.com/57s3l If you click on most of the red-marked tests, you'll find that the output seems to show that they actually pass!! Is there something wrong with the report generation tool? Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

RE: [boost] [config] _WIN32 question
by Ferdinand Prantl 16 Jul '04

16 Jul '04

Hi Volodya, > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of Vladimir Prus > [snip] > Does it mean I have to use the same conditional? Which > compilers define __WIN32__ or WIN32, but don't define _WIN32? > Shouldn't there be a single BOOST_WINDOWS macros to help in > this cases? The macro _WIN32 was originally hard-coded into the Microsoft compiler to recognize the platform. The other vendors took it the same way, but maybe because of rapid development in the early ages there are more underscored versions available... Here we are macros *32*, as they are defined: Borland: __WIN32__ _WIN32 Digital Mars: _WIN32 GCC (MinG/W and Cygwin with -mno-cygwin): __MINGW32__ WIN32 _WIN32 __WIN32 __WIN32__ Metrowerks: _WIN32 Microsoft: _WIN32 The macro WIN32 is meant to be a user-definable option how to enforce a WIN32 code if a compiler does not define _WIN32. Cygwin platform in POSIX mode is not a WIN32-compatible platform (no headers, no libraries), and thus their macros should mark a POSIX code, not Windows: GCC (Cygwin in POSIX mode): __CYGWIN__ __CYGWIN32__ > FWIW, filesystem defines such macro internally: > > # if !defined( BOOST_WINDOWS ) && !defined( BOOST_POSIX ) > # if defined(_WIN32) || defined(__WIN32__) || defined(WIN32) > || defined(__CYGWIN__) > # define BOOST_WINDOWS > # else > # define BOOST_POSIX > # endif > # endif I like the single BOOST_XXX macro idea for all libraries, I would only delete __CYGWIN__, which defines POSIX compatibility. And if you like, it is possible to do something like this to be complete: BOOST_WIN32 : _WIN32 || WIN32 BOOST_WIN64 : _WIN64| WIN64 BOOST_WINDOWS : BOOST_WIN32 || BOOST_WIN64 Ferda > - Volodya

2 1

[1.32 release] TODO list synchronization
by Aleksey Gurtovoy 16 Jul '04

16 Jul '04

As we are coming closer to the branch-for-release date, I'd like to inquire developers working towards the release about the current status of their corresponding TODO items below. Simply replying to this message and saying "Done", "Not done, will be done by date X", "Abandoned" or whatever you wish to say on each of the items would be more than fine. > Circular Buffer > /////////////// > > Pavel Vozenilek writes: > > I asked Jan Galdun and he will try to make circular_buffer available > for 1.32. > > > Date-Time > ///////// > > Jeff Garland writes: > > And while I'm on the subject date-time plans for release, the only 'major > issue' for this release is whether we are switching to boost-book for this > release. We would like to, but if we don't make it we will do it for the next > release. > > > Iterators > ///////// > > David Abrahams writes: > > There are a couple of things that ideally I would like to handle, but > which I am not promising (yet): > > 1. Minor adjustments to code in the iterators library > 2. Iterators library doc fixes > > > MPL > /// > > New version of the library will be checked in the main trunk before July 11. Not done yet; July 15 is the new target. > > > Multi-Index > /////////// > > Joaquín Mª López Muñoz writes: > > Current status: commited in the CVS since 6 weeks or > so. Regression tests are OK for all the compilers that > I intend to support. If someone is interested in some > other compiler being supported, please contact me. > > Pending issues: > #1 Minor updates to the docs. No big deal. > #2 Some changes related to the new defect macro > BOOST_NO_POINTER_TO_MEMBER_TEMPLATE_PARAMETERS > > These issues will be resolved way before the branching > date, I hope. > > > Numeric Conversions > /////////////////// > > Fernando Cacciola writes: > > In preparation for the upcoming 1.32 release I added this library to CVS. > The code and docs have been changed according to the extensive review > results. > I still need to extend the documentation adding examples and motivating > cases though, which I plan to do before the release. > > I haven't yet changed "boost/cast.hpp" to use the new stuff, I will as soon > as I see the code stablilized among different compilers. > > In the meantime, new users can use "boost/numeric/conversion/cast.hpp" which > contains the new version of numeric_cast<> > > > Program Options > /////////////// > > Vladimir Prus writes: > > 1. Add markup for the current failures on Windows. I've done all workarounds I > planned. > 2. Finally get some results on gcc2.95-stlport. I expect that the library > should work there, but due to Boost.Test failure I don't have any results. > 3. Try to make Sun compiler happy. I'm comitted a workaround some time ago, > but tests on Solaris were not run since then. > 4. Check dynamic linking on Windows. > > > Serialization > ///////////// > > Robert Ramey writes: > > I would very much like to see the serialization library in the 1.32 Release. > However, I'm not sure it will be possible to make the posted schedule. > > I have made all changes to address issues raised in the review. On my > personal machine I have passed tests for the compilers VC 7.1 VC 6, gcc 3.3. > Borland compiles (almost everything but requires some debug - it will pass > most tests) Comeau- compiles everthing - accept for a show stopping problem > I've been unable to resolve. My intention has been: > > a) post version compatible with 1.31 next week. > > b) build and test against the CVS tree on my computer > > c) check in > > In order to do this I need: > > a) authority to check in > > b) information on how to mark tests/compilers known to fail. > > c) I have a couple of questions that I need an expert opinion on. > > i) the first one is that in order to work, versions for vc 6.0 and > borland need to be compiled with spirit 1.61. So the a special > environmental variable indicating the directory path where this version of > spirit is located on the testing machine. SPIRIT_ROOT. This variable has > to be set when serialization libraries are built for these compilers. > > I should say I'm more than a little bit concerned about changes to mpl and > iterators. I'm very much aware of the delays and difficulties associated > with the 1.31 release - and it didn't even include this package. > > So I would like to continue on the path I've established above and we'll see > where things stand July 16 when/if you are ready to branch for release. > > > String Algorithms > ///////////////// > > Pavol Droba writes: > > I have few outstanding issues to fix, but they are mostly related to > the documentation. I think, I can manage it. > > As it seems, that the Range library will not make it to this release, > I will use the internal versions of facilities that are currently in the string_algo lib. > > So my todo list is as follows: > > 1) Finish the documentation > - Add functions list > - Add exception specifications > - Cleanup > > 2) Fix examples > 3) If there will be time, improve find_iterator > 4) Fix possible regressions. > > > Questions: > - I have posted some requestes/bugs on the boost-doc list. What is the status > of this. Will they be fixed before release? > > - According to metacom's tables regex is failing on comeau a so string_algo regex > test. Is this a setup or regex problem? > > - There is an problem with Intel compiler, split tests are failing and I cannot figureout > why. The message is very vague. Could somebody with an access to this platform, > try to debug the cause of the problem? > > - In regards to the older compiler support. I cannot resonably support compilers, that I > don't have an access to. Therefor if somebody is interested to use string_algo library > with one of such compilers, I will need an active help with porting. > > > uBLAS > ///// > > Michael Stevens writes: > > The current status of uBLAS is that it has been relatively untouched in the > Boost CVS single 1.30.0. The active development takes place on a separate > CVS. > > Therefore now would be a good time to bring in the latest code which as some > quite significant improvements. The code is relatively stable and tested on > core compilers. > > Issues: > On exotic (old) compiler the code is relatively untested and expected to fail. > Therefore the real need with regard to 1.32 is to get feedback from extensive > regression testing results in good time. > > As ever the documentation could do with further work to bring it up to date > with the to be release version. Thanks in advance, -- Aleksey Gurtovoy MetaCommunications Engineering

10 26

lexical_cast reviewed
by Jason 16 Jul '04

16 Jul '04

after fidling around with template functions i discovered you could write lexical_cast without any template arguments _required_. Also I neat little C-Style cast although no one is probably interested in using that. Anyways the syntax is as followed for both: // lexical cast improved: string str = lexical_cast( 3.1415f ); int i = lexical_cast( "12345" ); // C-style cast fun! string str = (cstyle_cast)3.1415f; int i = (cstyle_cast)"12345"; I would say that anyone already using lexical_cast would'nt have a problem with the improved one. Let me know what you guys think and if we should implement that. -Jason SOURCE CODE: #include <sstream> using namespace std; class cstyle_cast { public: template <typename Source> cstyle_cast( const Source & source ) { ss << source; } template <typename Target> operator Target() { Target target; ss >> target; return target; } private: stringstream ss; }; class lexical_cast { public: template <typename Source> lexical_cast( const Source & source ) { ss << source; } template <typename Target> operator Target() { Target target; ss >> target; return target; } private: stringstream ss; }; int main() { string str1 = (cstyle_cast)3.141592f; string str2 = lexical_cast(3.141592f); }

2 1