- Boost - lists.boost.org

[1.33.0] VC 7.1 vs. SFINAE/type traits
by Mat Marcus 16 Aug '05

16 Aug '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In one of our projects, the following code produces some strange compilation errors under VC 7.1/boost 1.33.0. Can anyone suggest a workaround? - Mat #include <sstream> #include "boost/type_traits.hpp" #include "boost/utility/enable_if.hpp" template <typename EnumType> typename boost::enable_if<boost::is_enum<EnumType>, EnumType>::type operator ~ (EnumType a); std::stringstream t; -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.0.2 (Build 2424) iQA/AwUBQwIDTxIZBaoznf65EQKEyACgnVW7095czvJp1MMvNruggOxQfIQAn2Qs TAtl4P353L4rRplTeFJwW2kO =jqlu -----END PGP SIGNATURE-----

4 4

Boost::UTF
by Owen Anderson 16 Aug '05

16 Aug '05

Hello, I was looking on Google for a good means of dealing with UTF encoded text files, and I ran across the old postings about Alberto Barbati's UTF library for Boost. While I know that the old files are still around, is there any progress being made on this front? Or is this a dead-end? Because it's exactly what I was looking for! -Owen Anderson

7 6

boost 1.32: read_write_mutex assertion
by Slawomir Lisznianski 16 Aug '05

16 Aug '05

Hello, I'm using Boost.Threads read/write mutex with the writer scheduling priority. Under heavy load, from many threads, I'm getting the following assertion: <..>/boost/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:190: void boost::deta il::thread::read_write_mutex_impl<Mutex>::do_write_lock() [with Mutex = boost::mutex]: Assertion `++loop_count == 1' failed. Abort (core dumped) The system is Linux kernel 2.4.21 (SMP) with 4 CPUs (Intel XEON MP) and g++ 3.2.3 20030502 (Red Hat Linux 3.2.3-42). Has anyone else experienced a similar problem? Thanks, Slawomir

1 0

Re: [boost] boost dll versions
by Martin Bonner 16 Aug '05

16 Aug '05

----Original Message---- From: David Abrahams [mailto:dave@boost-consulting.com] Sent: 16 August 2005 14:19 To: boost(a)lists.boost.org Subject: Re: [boost] boost dll versions >> While the breadth of support has helped boost gain wide acceptance, >> it is also the single biggest fault of the library as well. > > ?? Breadth of support has many benefits and only a few costs, and most > of those fall on the library maintainers. Library users (ahem, like > you) might pay for a slight reduction in velocity, but that's all. No, there are two further costs that library users pay: a) Features that are not implemented because they are too hard on older compilers. b) Features that use a less convenient syntax because supporting the more convenient syntax is too hard on older compilers. c) Features that are not implemented because the library maintainer has spent her limited time on maintaining support for older compilers. Having said that, it sure makes it easier to get buy-in to boost if it doesn't involve a compiler upgrade! -- 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

Can't upload to the sandbox?
by John Maddock 16 Aug '05

16 Aug '05

Trying to upload to the sandbox I get the following errors: Warning: fopen(userstats/johnmaddock.stat): failed to open stream: Read-only file system in /home/groups/b/bo/boost-sandbox/htdocs/vault/include/functions.php on line 785 Warning: fclose(): supplied argument is not a valid stream resource in /home/groups/b/bo/boost-sandbox/htdocs/vault/include/functions.php on line 797 Warning: fopen(stats/2005/08/month.stats): failed to open stream: Read-only file system in /home/groups/b/bo/boost-sandbox/htdocs/vault/include/functions.php on line 346 Warning: fwrite(): supplied argument is not a valid stream resource in /home/groups/b/bo/boost-sandbox/htdocs/vault/include/functions.php on line 348 Warning: fclose(): supplied argument is not a valid stream resource in /home/groups/b/bo/boost-sandbox/htdocs/vault/include/functions.php on line 350 Warning: fopen(stats/2005/08/16): failed to open stream: Read-only file system in /home/groups/b/bo/boost-sandbox/htdocs/vault/include/functions.php on line 275 Warning: fwrite(): supplied argument is not a valid stream resource in /home/groups/b/bo/boost-sandbox/htdocs/vault/include/functions.php on line 277 Warning: fclose(): supplied argument is not a valid stream resource in /home/groups/b/bo/boost-sandbox/htdocs/vault/include/functions.php on line 279 The uploaded file appears in the list, but can't be accessed. Anyone any ideas what's wrong? Thanks, John.

2 2

[regex] 1.33 missing include causes compile error... MIPS Pro 7.4.1
by Kevin Wheatley 16 Aug '05

16 Aug '05

cpp_regex_traits.hpp appears to be missing an include to define std::basic_istream<> ... cc-1070 CC: ERROR File = boost_1_33_0/boost/regex/v4/cpp_regex_traits.hpp, Line = 442 The indicated type is incomplete. std::basic_istream<charT> m_is; // stream for parsing numbers. ^ A template was detected during header processing. instantiation of class "boost::re_detail::cpp_regex_traits_implementation<char>" at line 945 instantiation of "std::string boost::cpp_regex_traits<char>::error_string(boost::regex_ constants::error_type) const" at line 171 of "boost_1_33_0/libs/regex/build/../src/posix_api.cpp" 1 error detected in the compilation of "boost_1_33_0/libs/regex/build/../src/posix_api.cpp". So the attatched patch adds a suitable include to get regex compiling Kevin -- | Kevin Wheatley, Cinesite (Europe) Ltd | Nobody thinks this | | Senior Technology | My employer for certain | | And Network Systems Architect | Not even myself | --- boost_1_33_0_mipspro_7.4.1/include/boost-1_33/boost/regex/v4/cpp_regex_traits.hpp 2005-07-12 10:49:10.000000000 +0100 +++ boost_1_33_0/boost/regex/v4/cpp_regex_traits.hpp 2005-08-16 14:32:00.000000000 +0100 @@ -21,6 +21,8 @@ #include <boost/config.hpp> +#include <istream> + #ifndef BOOST_NO_STD_LOCALE #ifndef BOOST_RE_PAT_EXCEPT_HPP

2 1

[regex] MipsPro failure in boost/regex/v4/fileiter.hpp (1.33.0)
by Richard Hadsell 16 Aug '05

16 Aug '05

The mipspro build of regex fails in fileiter.cpp, because the header is missing an include: mipspro-C++-action bin/boost/libs/regex/build/libboost_regex.so/mipspro/debug/fileiter.o cc-1079 CC: ERROR File = /tmp_mnt/netDISKS/cgi/IRIX4/cgi/vendor/library/boost/boost_1_33_0/boost/regex/v4/fileiter.hpp, Line = 212 A type specifier is expected. typedef std::ptrdiff_t difference_type; ^ ... (2 similar places in the same file) The fix should be good for any compiler: diff -u -r1.1 -r1.2 --- boost/regex/v4/fileiter.hpp 2005/08/12 17:26:18 1.1 +++ boost/regex/v4/fileiter.hpp 2005/08/16 16:49:48 1.2 @@ -61,6 +61,7 @@ #elif defined(BOOST_REGEX_FI_POSIX_DIR) +#include <cstddef> #include <cstdio> #include <cctype> #include <iterator> P.S.: Thanks to Kevin Wheatley for reporting a similar problem in cpp_regex_traits.hpp, so that I didn't have to. -- Dick Hadsell 914-259-6320 Fax: 914-259-6499 Reply-to: hadsell(a)blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 44 South Broadway, White Plains, NY 10601

1 0

Boost regression notification (2005-08-16)
by Douglas Gregor 16 Aug '05

16 Aug '05

Boost regression test failures ------------------------------ Report time: 2005-08-16T14:49:25Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 107 failures in 7 libraries: graph (11) iostreams (3) numeric/ublas (1) parameter (69) regex (1) serialization (21) wave (1) |graph| graphviz_test: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux mingw-3_4_2 vc-7_1 vc-7_1 vc-7_1 |iostreams| bzip2_test: mingw-3_4_2 gzip_test: mingw-3_4_2 zlib_test: mingw-3_4_2 |numeric/ublas| test3: intel-8.1-linux |parameter| basics: borland-5_6_4 cw-8_3 cw-9_4 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 intel-8.1-linux intel-win32-9_0 msvc vc-6_5 vc-6_5-stlport vc-7_0 macros: borland-5_6_4 cw-8_3 cw-9_4 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 intel-8.1-linux intel-win32-9_0 msvc vc-6_5 vc-6_5-stlport vc-7_0 sfinae: borland-5_6_4 cw-8_3 cw-9_4 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 intel-8.1-linux intel-win32-9_0 msvc vc-6_5 vc-6_5-stlport vc-7_0 unnamed: borland-5_6_4 cw-8_3 cw-9_4 cw-9_4 cw-9_5-darwin gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-6_5 vc-6_5-stlport vc-7_0 vc-7_1 vc-7_1 vc-7_1 |regex| concept_check: gcc-3.2.3-linux |serialization| test_class_info_load_binary_archive: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_binary_archive_dll: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_text_archive: gcc-3_4_3-sunos test_class_info_load_text_archive_dll: gcc-3_4_3-sunos test_class_info_load_text_warchive: gcc-3_4_3-sunos test_class_info_load_text_warchive_dll: gcc-3_4_3-sunos test_class_info_load_xml_archive: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_xml_archive_dll: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_xml_warchive: gcc-3_4_3-sunos test_class_info_load_xml_warchive_dll: gcc-3_4_3-sunos 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_shared_ptr_132_text_archive: gcc-3.2.3-linux |wave| testwave: gcc-3.3.6-linux

1 0

Re: [boost] Propose adding Clone Smart Pointer (clone_ptr) to the boost library
by Eyal Farago 16 Aug '05

16 Aug '05

besides implementation issues regarding proper creation and destruction of a clone_ptr, it seems that you're trying to achieve few goals in one class. you're talking about the clone problem which is a complete problem on its own and then you're talking about pointers in stl containers and algorithms, and as a result you came out with a class that tries to solve both problems. these two problems are completeley unrelated, you can itroduce a simple adaptor that modifies an existing pointer type (smart or not...) into a comparable class (I've implemented one in a few minutes) and you can write a seperate class that takes care of clowning (possible or not, I don't know, follow the thread), then you can wrap it all together using a typedef and get a simpler, more flaxible and robust design. then you can readopt the entire thing using another adaptor... (*i.e. copy on write.) by the way, this is the approach taken by the iterator adaptors library, if you need a filter and transform iterator you simply apply a transform iterator adaptor to a filter iterator adaptor applied to the base iterator. eyal. -----Original Message----- From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org]On Behalf Of Martin Bonner Sent: Tuesday, August 16, 2005 12:17 PM To: 'boost(a)lists.boost.org' Subject: Re: [boost] Propose adding Clone Smart Pointer (clone_ptr) to the boost library ----Original Message---- From: Axter [mailto:boost@axter.com] Sent: 16 August 2005 03:39 To: boost(a)lists.boost.org Subject: [boost] Propose adding Clone Smart Pointer (clone_ptr) to the boost library > I'm proposing to add the clone_ptr class to the boost library. > > I've developed a clone_ptr class that performs a clone of an abstract > pointer without the need for a clone method. > > The clone_ptr is well suited for automatic deep copy of abstract > pointers, > and for use with STL containers. > > In addition to being able to perform clone operations, it also have > operators that performs comparison on the object being pointed to, > instead > of the pointer address. > This allows for correct sorting and comparison of clone_ptr's in an > STL > container. > See following link for more info: > http://code.axter.com/clone_ptr_introduction.htm I was interested in the example you give in the web page: class foo { clone_ptr < AbstractClass > m_MyAbstractClassPtr; public: foo(AbstractClass * abstractclassptr_):m_MyAbstractClassPtr(abstractclassptr_){} foo(const foo& Src) { //In the following line of code, the clone pointer will copy the // correct derived class without the need of a clone method m_MyAbstractClassPtr = Src.m_MyAbstractClassPtr; } }; That looked a very clever trick. I couldn't see how clone_ptr was going to copy the dynamic type of the argument to the constructor without any information about that dynamic type. Having looked at the code, I don't think it does. It would work if the constructor was declared: foo(DerivedClass*p): m_MyAbstractClassPtr(p) {} or even template <class Derived> foo(Derived *p):m_MyAbstractClassPtr(p) {} but even that will fail if the constructor is called via: Derived *p = new DerivedDerived; foo foo_obj(p); My basic concern is that while clone_ptr could be useful, it only works if people stick rigidly to certain rules. Those rules need to be made VERY clear, otherwise it provides a plentiful supply of rope. It would also be useful to have some documentation of what methods clone_ptr provides, and what effects they have. -- 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

1 0

Re: [boost] boost dll versions
by Martin Bonner 16 Aug '05

16 Aug '05

----Original Message---- From: Martin Bonner [mailto:martin.bonner@pitechnology.com] Sent: 16 August 2005 14:55 To: 'boost(a)lists.boost.org' Subject: Re: [boost] boost dll versions > No, there are two further costs [snip] ^^^ > a) [snip] > b) [snip] > c) [snip] Humph. That's why I usually use a computer to do my counting for me :-( -- 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