October 2004 - Boost - lists.boost.org

Sprit-1.6 and latest boost
by Russell Hind 20 Oct '04

20 Oct '04

Because bcc32 can't deal with spirit-1.8, to use spirit and boost 1.31, I've replaced spirit.hpp and the spirit directory in boost with the 1.6 distribution. This doesn't work with the latest boost code, it looks like the errors are due to the changes mpl that were mentioned. Are there any plans to update spirit 1.6 to work with latest boost so those of us with older compilers can use the two together? Thanks Russell

3 9

Boost 1.31.0 just announced on freshmeat??
by Neal D. Becker 20 Oct '04

20 Oct '04

What's this? http://freshmeat.net/projects/boost/?branch_id=3248&release_id=176309

2 1

RE: [boost] Re: Any interest in adding unicode support to boost?
by Stefan Seefeld 20 Oct '04

20 Oct '04

> From: Robert Ramey [mailto:ramey@rrsd.com] > Sent: October 19, 2004 12:19 > So I always presumed that there was a "unicode" locale that > implemented this > as well all other required information. Now that I think > about it I realize > that it was only a presumption that I never really checked. > Now I wonder > what facitlities do most libraries do provide for unicode > facets. I know > there are ansi functions for translating between multi-byte and wide > character strings. I've used these functions and they did > what I expected > them to do. I presumed they worked in accordance with the currently > selected locale and its related facets. If the > basic_string<wchar_t>::operator<(...) isn't doing "the right > thing" wouldn't > it be just a bug in the implementation of the standard > library rather than a > candidate for a boost library? The unicode standard is rather young, compared to the C++ standard library. It seems the original authors of std::locale and std::basic_string just prepared for some expected flexibility. That doesn't mean all the complexities of today's unicode could fit into that. Just look at the size requirements alone compared to 'wchar_t'... Regards, Stefan

2 1

ATTN: Branch for release completed
by Aleksey Gurtovoy 20 Oct '04

20 Oct '04

Per our standard conventions, the branch tag is "RC_1_32_0", and the main trunk state from which the branch was performed is tagged as "merged_to_RC_1_32_0". Please see http://www.boost.org/more/release_procedures.htm#Developers for a detailed procedure for merging fixes between the branch and the main trunk. To regression runners using "regression.py" driver: to switch the tests to run on the branch, you need to specify the branch name in the script's command line using the '--tag': python regression.py --tag=RC_1_32_0 ... -- Aleksey Gurtovoy MetaCommunications Engineering

2 1

ATTN: Branch for release starts in 10 minutes
by Aleksey Gurtovoy 20 Oct '04

20 Oct '04

Please do not check in anything into the main trunk until further notice. -- Aleksey Gurtovoy MetaCommunications Engineering

1 0

Re:Re: [boost] Re: serialization - build shared libs
by Robert Ramey 20 Oct '04

20 Oct '04

Martin Ecker wrote: >Neal Becker wrote: >> Is this perhaps a MS-windows specific problem? I did build a shared lib >> (using scons, I haven't learned jam yet), and AFAICT it is working, on >> Linux. >I'm pretty sure you will also run into problems with shared objects >under Linux. The problem is that certain global variables (e.g. for >the type registry) are defined as static member variables in header >files. Under Windows, if two different DLLs include this header file, >you will get two different copies of that static member variable - one >in each DLL - although there should only be one. Maybe the linker >under Linux is smart enough to resolve such issues. >Have you tried to serialize a class defined in one shared object > (which is registered in the type registry via BOOST_CLASS_EXPORT) from >code in another shared object? That's when you might run into >problems. You definitely will under Windows. >You might also run into problems when you dynamically (i.e. explicitly >in your code via dlopen) load a shared object, which contains classes >that use BOOST_CLASS_EXPORT to register themselves. Again, under >Windows you definitely will. I think there is a little confusion here about what it means to build the serialization library as a Shared Library or DLL. a) if you mean creating libraries which contain exactly the same functionality as libboost_serialiation.lib and libboost_wseralization.lib then there should be no problem as far as I know. Note that you might have problems if you loading/unloading the shared libraries multiple times under program control. I'm not sure. I haven't tested this and have left it for latter. Mainly this is because it should use the ABI autolink to be line with other boost libraries and work better for users. b) if you creating DLLS which instantiate serialization templates for specific classes - then you most likely have problems. There are still some issues pending. Martin has jumped ahead and addressed these issues for his application and most of his additions will likely eventually find their way into the serialization library in some form. Robert Ramey

4 16

[fsm] New release
by Andreas Huber 20 Oct '04

20 Oct '04

Dear Boosters I've finally managed to address the main issues that were raised in the last discussion on boost::fsm (exit() and BOOST_FSM_RELAX_TRANSITION_CONTEXT). Code and documentation should now be reasonably close to what will undergo the formal review. The only thing that is still lacking are proper tests, which I'll try to implement in the next few weeks. The .zip can be found here: http://boost-sandbox.sf.net/fsm.zip The docs are also available online: http://boost-sandbox.sf.net/libs/fsm As always: Feedback is highly welcome. Thanks & Regards, -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.

1 0

RE: [boost] Re: Any interest in adding unicode support to boost?
by Bennett, Patrick 19 Oct '04

19 Oct '04

> On Behalf Of Erik Wien > Sent: Tuesday, October 19, 2004 11:09 AM > To: boost(a)lists.boost.org > Subject: [boost] Re: Any interest in adding unicode support to boost? > > ----- Original Message ----- > From: "Patrick Bennett" <patrick.bennett(a)inin.com> > > > Erik, be sure to take a look at IBM's open-source ICU library: > > http://oss.software.ibm.com/icu/ > > I have looked at the ICU library, and it's a very good unicode > implementation, but the goal of my project will be to create a library > that is in a form that could be standardized in boost, and from what > have seen/read, ICU is not really suited for that. [Bennett, Patrick] Agreed. I just wanted to make sure you took a look at it, minimally, as a guide or reference, as it is quite extensive. > If the ICU licence is boost compatible, it would be possible to base an > implementation on ICU however, but that will be determined if the project > is approved by my college. [Bennett, Patrick] If it matters, ICU's license is about as simple as it gets.

1 0

david_abraham's lock in CVS
by Russell Hind 19 Oct '04

19 Oct '04

Trying to check out CVS: and am getting cvs checkout: [08:31:45] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v2/test/dependency-test/src1 For more than half an hour. How long to these take to expire? Thanks Russell

2 1

patch to build boost on dragonflybsd
by Patrick Mauritz 19 Oct '04

19 Oct '04

the attached patch makes it possible to build boost on dragonflybsd with gcc3.4. the change in boost/python/detail/config.hpp is necessary as dfly doesn't provide the gcc-patched headers that "fix" offsetof(). if defined(freebsd)&&!defined(dragonfly) is in there as dfly sometimes defines both of them. after this patch, everything except boost::serialize (which complains about lack of wchar_t) should build. patrick mauritz

2 1