November 2007 - Boost - lists.boost.org

[range] range_size<T> deprecation, updated docs etc.
by Thorsten Ottosen 15 Nov '07

15 Nov '07

Dear all, As suggested by several people, I have started to rely on range_difference<T>::type in all places of the library. I have also updated the docs w.r.t new concepts and are working on polishing them. 1.35 will introduce a new function template< class T > BOOST_DEDUCED_TYPENAME range_difference<T>::type size( const T& r ); that requires T to be a random access range. I also want to put a post-condition saying "result >= 0", but was a bit in doubt when I read the standards wording for std::distance(): "template<class InputIterator> typename iterator_traits<InputIterator>::difference_type distance(InputIterator first, InputIterator last); 4 Effects: Returns the number of increments or decrements needed to get from first to last. 5 Requires: last shall be reachable from first." How can one ever use decrements to get from first to last? Any comments? -Thorsten

7 10

[threads] Exception handling change on Windows?
by Beman Dawes 15 Nov '07

15 Nov '07

Starting right about the time of the revision 41056 threads changes, the Windows smoke tests started to pop up dialog boxes (rather than just failing quietly) for various threads problems. bjam had not been recompiled, and there was nothing else running on the machine at the time. Is this a threads problem, or did something go haywire on my machine? --Beman

6 11

[regex][bug]Regex::regex_search does not handle /b&/B correclty in Win32
by Hakuro 15 Nov '07

15 Nov '07

Hello Folks. I found an issue of regex_search() with "/b" or "/B" assertion in Win32 and created a patch(attached). Please review it. Issue: /b, /B does not match with several word boundaries. i.e. regPat = /\bis\b/; regPat.exec("This\u00C0is\u00C0bad"); //Does not match regPat.exec("Thisあisあbad"); // Does not match Desc: In the ECMA262 regex spec(15.10.2.6), for "/b" and "/B" assertion only charaters [0-9A-Za-z_] are allowed as a word character and other should be treated as out of word. In the boost:regex inpmenetation for Win32, GetStringTypeEx() with C1_ALPHA | C1_DIGIT flags is used to determine char type. However the API does not differentiate [0-9A-Za-z_] and other characters (e.g. European characters, Kanji) (just linguistic characters and everybody else) which does not meet the spec. Patch: Patch for w32_regex_traits.hpp, attached. Modified isctype() to determine character type without the API use. Regards. Hak Matsuda Lead Dev. CRI Middleware inc. 340 Brannan St #400, San Francisco, CA 94107 -- Thanks! HAK

2 1

[wave] msvc-8.0 warning patch
by Juergen Hunold 15 Nov '07

15 Nov '07

Hi ! Compiling Boost.Wave with msvc-8.0 issues lots of Microsoft's "deprecated" warnings. Please find a patch attached. Okay to commit ? Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

2 2

Re: [boost] [interprocess] HP-UX_ia64_gcc test failingduetopermissions
by Ion Gaztañaga 15 Nov '07

15 Nov '07

Boris Gubenko wrote: > You might want to reconsider how you create name argument for shm_open() > function, at least on the platforms with filesystem-based implementation. > In your example, the name begins with a slash and Interprocess library > passes it to shm_open() untouched. But prepending the slash makes even > "innocent" call like > > shared_memory_object(create_only, "foo", read_write); > > to fail. Perhaps, you can use name transformation algorithm which is > currently used on the platforms where > BOOST_INTERPROCESS_POSIX_SHARED_MEMORY_OBJECTS macro is not defined > on the platforms where this macro is defined as well. Just a thought. According to the opengroup specification: http://www.opengroup.org/onlinepubs/007908799/xsh/shm_open.html The name argument conforms to the construction rules for a pathname. If name begins with the slash character, then processes calling shm_open() with the same value of name refer to the same shared memory object, as long as that name has not been removed. If name does not begin with the slash character, the effect is implementation-dependent. The interpretation of slash characters other than the leading slash character in name is implementation-dependent. So: -> If leading slash is not used, two processes might not access the same memory. -> If there are more slashes than the leading one, both processes refer the same shared memory but that name is not portable accross OSs. -> The only portable (between OSs) name is a name that only has a leading slash. In all POSIX books the recommended name format is "/name", (in fact, some systems don't accept a name without the leading slash). In Linux /name leading to a shared memory created in /dev/shm/name. Then I have two options: -> Transform internally the name for HP-UX to a directory where everyone can create shared memory. What should I choose? /tmp? -> Change names used in tests for HP-UX for something that works. It's a shame that there is no portable shared memory name for every system ;-), because many pages, like these: http://www.tin.org/bin/man.cgi?section=3&topic=shm_open http://linux.die.net/man/3/shm_open or some POSIX books say: "For portable use, name should have an initial slash (/) and contain no embedded slashes." I wasn't expecting permission problems, though ;-) Could you tell me a shared memory name that a user could use successfully in HP-UX? Thanks for your quick reply, it's been really helpful. Ion

2 4

[regex][bug]Regex::regex_search does not handle /B outside the word case correclty
by Hakuro 15 Nov '07

15 Nov '07

Hello again. I found another issue of regex_search and created a patch for it, too. Please review it. Issue: regex_search() with "/B" is handling inside a word case correctly but not handing outside the word case correctly. i.e. regPat = /\B\u00c0/; regPat.exec("\u00C0\u00C0\u00C0"); //Should match but not Desc: In the ECMA262 spec(15.10.2.6), "\B" behavior is described as follows. 1. Let e be x's endIndex. 2. Call IsWordChar(e–1) and let a be the boolean result. 3. Call IsWordChar(e) and let b be the boolean result. 4. If a is true and b is false, return false. 5. If a is false and b is true, return false. 6. Return true. So it should match outside a word case not only inside case. (A word character list is [A-Za-z0-9_]). Patch: Patch for perl_matcher_common.hpp, attached. Modified match_within_word() to follow the spec. Regards. Hak Matsuda Lead Dev. CRI Middleware inc. 340 Brannan St #400, San Francisco, CA 94107

1 0

[test][gcc-4.3.0][trunk] missing include in boost/test/impl/debug.ipp
by "JOAQUIN LOPEZ MU?Z" 14 Nov '07

14 Nov '07

The trunk version of boost/test/impl/debug.ipp uses std::memcpy without having included an appropriate header, as shown in http://tinyurl.com/yt3hv8 : [...] In file included from ../boost/test/included/unit_test.hpp:19, from ../libs/test/test/online_test.cpp:17: ../boost/test/impl/debug.ipp: In function ???char* boost::debug::<unnamed> ::copy_arg(boost::debug::<unnamed>::mbuffer&, boost::unit_test::const_string)???: ../boost/test/impl/debug.ipp:338: error: ???memcpy??? is not a member of ???std??? [...] Curiously enough it is only GCC 4.3.0 that catches the problem, probably because std::memcpy is implicitly included by some header or another in all other platforms. The attached patch should solve the problem. OK to commit? Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

4 6

[serialization] msvc-8.0 warnings patch
by Juergen Hunold 14 Nov '07

14 Nov '07

Hi ! Building Boost.Serialization with msvc-8.0 issues lots of Microsoft's "deprecated warnings. Please find a patch for serialization/Jamfile.v2 attached. Okay to commit ? Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

1 0

[rfc] Flyweight library
by "JOAQUIN LOPEZ MU?Z" 14 Nov '07

14 Nov '07

Hi all, After a year since the last published draft, I think the flyweight library I'm working on is in a sufficiently polished state to issue a request for comments on its usefulness and eventual suitability for inclusion into the Boost review queue. * Abstract: Flyweights are small-sized handle classes granting constant access to shared common data, thus allowing for the management of large amounts of entities within reasonable memory limits. Boost.Flyweight makes it easy to use this common programming idiom by providing the class template flyweight<T>, which acts as a drop-in replacement for const T. * Design: The flyweight library is a relatively small piece of software that tries to combine both maximum simplicity of usage for casual users and great flexibility for those programmers needing to control aspects of the implementation. Configuration and customization rely upon a very extensive policy interface, whose syntax is kept under control thanks to the Boost Parameter Library. The following aspects can be controlled: - Specification and parameterization of the so-called flyweight factory. - Control of the factory instantiation procedure. - Specification of the internal synchronization mechanisms. - Flyweight tracking, allowing for the disposal of stored values when no longer referenced by any flyweight object. The library provides a catalog of plug-in components, but the user can also supply her own as the needed concepts are publicly documented. In particular, an insidious problem with duplication of flyweight factories across dynamic modules is taken care of by a component called intermodule_holder, whose implementation is based on Boost.Interprocess. * Download: Boost Vault, folder Patterns (http://tinyurl.com/hrdm6 ), file flyweight.zip. * Online docs: http://tinyurl.com/2jbucf . * Usage: Will only work with the trunk version of Boost, daily snapshot at http://boost-consulting.com/boost.tar.bz2 . Currently, serialization capabilities are not working, pending the resolution of the issue exposed at http://lists.boost.org/Archives/boost/2007/09/127065.php . * Tested on: GCC 3.4.4 on mingw, MSVC++ 8.0. Comments, suggestions, cricitisms, are most welcome. I would also like to know if there's interest in having this included in the review queue. Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

11 11

Re: [boost] Contents of Boost digest Vol 2004, Issue 4 - Re: Boost::Serialization (XML in specific)
by Drew Hohmann 14 Nov '07

14 Nov '07

>> I am saving multiple classes which contain STL collections, and in turn >> those STL collections contain classes that contain more STL collections. >> A sample XML file follows. >> >> The problem occurs when I try and move the XML file into a database, and >> I receive the error "The table (item) cannot be the child table to >> itself in nested relations." >I'm not sure I understand what the problem is. Is the generated XML file >well-formed ? Is it valid, according to whatever document-type >definition might exist ? > >It sounds as if your database imposes additional constraints (unrelated >to XML), that are not met by the XML-generation of boost.serialization. > >If that's the case, may be you can post-process the XML by renaming >certain nodes (using an XSLT transformation, say) ? > >Regards, > Stefan The XML is valid and correct. I'd like to derive a serialization class which can write directly into a database, which would bypass saving to XML then importing into a database. Obviously the derived class would have to resolve the nested table issue. I think the XML serialization would be useful to more people if it didn't create different tables with the same name. Drew

1 0