- Boost - lists.boost.org

[lexical_cast] specializing
by Maxim Yegorushkin 22 Jun '05

22 Jun '05

I'd like to be able to specialize lexical_cast for certain source->target conversions. With its current design I see no possibility to do that as function templates can not be partially specialized. Are the any plans to change that? -- Maxim Yegorushkin

3 6

Re: [boost] Boost::regex match prefix problem
by A. Johan 22 Jun '05

22 Jun '05

Thanks John! Will try the cvs then. Cheers. Alfonso Johan Soft Switch Sdn. Bhd. Kuala Lumpur, Malaysia http://www.softswitch.com.my -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.7.10/25 - Release Date: 21/06/2005

1 0

[filesystem 1.32.0] bug in name checking for win32 native paths
by Russell Hind 22 Jun '05

22 Jun '05

I have two paths, both set to c:\ and if I concatenate them using operator /, I get a resultant path of c:\c:\ which is invalid, but the namechecking doesn't throw an execption. e.g. void test(void) { boost::filesystem::path p("C:\\", boost::filesystem::native); boost::filesystem::path p2(p); p2 = p2 / p; } p2 results as "c:/c:/" (the internal representation). Cheers Russell

2 1

Boost::regex match prefix problem
by A. Johan 22 Jun '05

22 Jun '05

Hello all, I'm developing an application that uses boost::regex library and ms visual c++ 2003 (7.1). I'm trying to split a string into a smaller set of strings by using regex_split. However I would like to skip if the split character is prefixed by \. Typically I would use the following regex - (?<!\\); Where in c++ it would be something like std::string s("(?<!\\\\);") Compiles ok but I will get an exception when I try to use it as a parameter to the regex - boost::regex(s) So would appreciate any pointers or ideas or am I just doing I plainly wrong? Cheers & have a good day all. A. Johan -- "The roof, the roof, the roof is on fire..." -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.7.10/25 - Release Date: 21/06/2005

2 1

Re: [boost] Boost.config not recognize threading support enabled?
by BRIDGES Dick 22 Jun '05

22 Jun '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] On > Behalf Of John Maddock > Sent: Saturday, June 18, 2005 4:31 AM > To: boost(a)lists.boost.org > Subject: Re: [boost] Boost.config not recognize threading support enabled? <snip> > If you look at the line that triggers the #error, you will see it is within > a block scoped by: > > #elif !defined(BOOST_HAS_THREADS) > > so the error is triggered by BOOST_HAS_THREADS not being defined. If you > now grep through the boost/config headers you will see: > > In suffix.hpp: > > #if (defined(__MT__) || defined(_MT) || defined(_REENTRANT) \ > || defined(_PTHREADS)) && !defined(BOOST_HAS_THREADS) > # define BOOST_HAS_THREADS > #endif <snip> > To find out which of the above is the cause the easiest way I find is to > through some #errors in the preprocessor branches you think may be taken and > then see if the #error is triggered or not (this is much easier than > preprocessing the code IMO). > > To help you more we probably need: > > The gcc version. [Dick] "/opt/crosstool/arm-softfloat-linux-gnu/gcc-3.3.3-glibc-2.3.2/bin/arm-so ftfloat-linux-gnu-c++" -v Reading specs from /opt/crosstool/arm-softfloat-linux-gnu/gcc-3.3.3-glibc-2.3.2/lib/gcc-lib /arm-softfloat-linux-gnu/3.3.3/specs Configured with: /data/work/OMAP/crosstool/crosstool-0.28-rc37/build/arm-softfloat-linux- gnu/gcc-3.3.3-glibc-2.3.2/gcc-3.3.3/configure --target=arm-softfloat-linux-gnu --host=i686-host_pc-linux-gnu --prefix=/opt/crosstool/arm-softfloat-linux-gnu/gcc-3.3.3-glibc-2.3.2 --with-float=soft --with-headers=/opt/crosstool/arm-softfloat-linux-gnu/gcc-3.3.3-glibc-2. 3.2/arm-softfloat-linux-gnu/include --with-local-prefix=/opt/crosstool/arm-softfloat-linux-gnu/gcc-3.3.3-gli bc-2.3.2/arm-softfloat-linux-gnu --disable-nls --enable-threads=posix --enable-symvers=gnu --enable-__cxa_atexit --enable-languages=c,c++ --enable-shared --enable-c99 --enable-long-long Thread model: posix gcc version 3.3.3 __GLIBCPP__ is 20040214 and __GLIBCXX__ is not defined. I 'peppered' the headers with #warningS and determined that: - BOOST_HAS_THREADS is not defined in gcc.hpp because linux, __linux & __linux__ are all defined. - BOOST_STDLIB_CONFIG is defined as "boost/config/stdlib/libstdcpp3.hpp" in select_stdlib_config.hpp. But BOOST_HAS_THREADS is not defined in libstdcpp3.hpp because __GLIBCXX__ is not defined. - BOOST_HAS_PTHREADS is defined in posix_features.hpp after <unistd.h> is included. I had hoped this was a good thing. ;) - Then we get to suffix.hpp. BOOST_HAS_PTHREADS is defined and BOOST_DISABLE_THREADS is !defined. So far, so good. However, because none of _REENTRANT, _PTHREADS, __MT__, and __MT are defined, BOOST_HAS_THREADS is still not defined. Consequently, on the way out, BOOST_HAS_PTHREADS is undef'D. Now that I see how BOOST_HAS_THREADS is not defined, I've moved into the dark nether region of the-land-way-over-my-head. I'm tempted to add BOOST_HAS_PTHREADS to the list of macros tested here: <snippet file=suffix.hpp> // Turn on threading support if the compiler thinks that it's in // multithreaded mode. We put this here because there are only a // limited number of macros that identify this (if there's any missing // from here then add to the appropriate compiler section): </snippet> *BUT*, that little parenthetical admonition strongly suggests this file is not to be modified - ever again. ;) Besides: there must have been a reason for defining BOOST_HAS_PTHREADS without automatically concluding BOOST_HAS_THREADS. Apparently a similar problem was fixed in the past (http://lists.boost.org/MailArchives/boost/msg19675.php) by adding an unconditional define of BOOST_HAS_THREADS to metrowerks.hpp. But that clearly won't work with gcc.hpp. I am sorely in need of guidance. Where should I go from here? > The command line that produced the above error. [Dick] "/opt/crosstool/arm-softfloat-linux-gnu/gcc-3.3.3-glibc-2.3.2/bin/arm-so ftfloat-linux-gnu-c++" -I/usr/local/boost_1_32_0 -pthread test.cpp > The output from the config_info program (cd into libs/config/test then > "bjam -sBUILD="<threading>multi" config_info", then look for output the > program generated somewhere under > boost-path/bin/boost/libs/config/test/config_info/ ...some directories... > /*.output [Dick] Hey, that's a NEAT tool! (Unfortunately the "default" compiler is gcc 3.4 and defines _REENTRANT. %>[ ) I'm going back through the docs now to figure out how to invoke the cross-compiler but hoping the above info might yield and answer. > Hope this gets you further forward. > > John. > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost [Dick] Your help with this is sincerely appreciated. Thank you.

2 1

Audiomatic is using Boost
by David Brownell 22 Jun '05

22 Jun '05

Application Name: Audiomatic Company Name: Wise Riddles Software About Audiomatic: Audiomatic is a tool used to make system-wide macros and then launch those macros with a voice command or keyboard shortcut at any time... from any Windows application. Audiomatic enables you to launch programs, files, or websites; simulate keystrokes; play sounds; speak text; or even run scripts. You can do it all with a voice command or keyboard shortcut! Libraries Used: bind, function, smart pointers, date/time, string, utility (noncopyable, ref), regex, thread, mpl, type traits Application URL: www.WiseRiddles.com/Audiomatic Company URL: www.WiseRiddles.com Application Type: Shrink wrapped Software Thank you for providing this resource and making this information available to other developers! David Brownell Wise Riddles Software www.WiseRiddles.com

2 1

Re: [boost] Who's Using Boost - Thankyou and updates
by Johannes Brunen 22 Jun '05

22 Jun '05

Hi, I have checked the entry for DataSolid at http://freespace.virgin.net/boost.regex/who/html/who_s_using_boost_/shrink.… and I have detected two small errors: 1. It would be fine to delete the phrase professional as the product line is just named 'CADdy++ Mechanical Design'. This was my fault, sorry. 2. 'CAFdy++ uses the ...' should be 'CADdy++ uses the ...' With best regards Johannes ____________ Virus checked by G DATA AntiVirusKit

2 1

Hydranode Project is using Boost libraries
by Alo Sarv 22 Jun '05

22 Jun '05

Hydranode Engine is a plugin-driven P2P client engine that relies heavily on Boost libraries. Hydranode codebase is licenced under GNU GPL, and is developed mainly by Alo Sarv. Currently in Beta phase, Hydranode runs on wide range of platforms, including Windows, Linux, BSD, Mac OS, Solaris etc. Hydranode Engine and plugins rely heavily on the following Boost libraries: Bind, Function, Lambda, MultiIndex, Signals, Threads, SmartPtr, Format, LexicalCast. Other Boost libraries being used include FileSystem, StringAlgo, DateTime, ProgramOptions, Spirit, Random, Tokenizer, TypeTraits, Tribool, Tuple and Any. Once Boost 1.33 is released, I'm also looking forward to using Boost.IOStreams library in Hydranode. All complex data structures in Hydranode are implemented using MultiIndex containers, which significantly reduced development time and kept code clean. Format is being used for all text formatting. Having Threads and FileSystem libraries available made cross-platform development lot easier in those areas. Homepage: http://hydranode.com/

1 0

Re: [boost] boost.filesystem on HPUX
by S G Ganesh 22 Jun '05

22 Jun '05

Hi Toon, Caleb Epstein, Beman, Thomas Matelich, >> > Does anybody now any other flag that might influence this? >> Is it normal (never used readdir_r myself) that it is only defined in >> > multi-threading-mode? >From manpage of readdir_r: "Users of readdir_r() should note that readdir_r() now conforms with the POSIX.1c Threads standard. The old prototype of readdir_r() is supported for compatibility with existing DCE applications only." _r denotes reentrant functions and -mt enables the following (for default -AA mode for aCC/Itanium): * -D_REENTRANT * -D_RW_MULTI_THREAD * -D_RWSTD_MULTI_THREAD * -D_POSIX_C_SOURCE=199506L * -D_HPUX_SOURCE * * -lpthread >> Should we instruct bbv1 to compile the boost.filesystem always with the -mt flag on hpux ? Yes. >> Yes that seems eminently reasonable (that readdir_r only be >> prototyped/available if -mt is supplied). Yes, since readdir_r is specifically for multithreaded code. >> Well, there is code in libs/filesystem/src/operations_posix_windows.cpp that attempts to >> detect if it is being compiled with multi-threading enabled: >> >> # if defined(_POSIX_THREAD_SAFE_FUNCTIONS) \ >> && defined(_SC_THREAD_SAFE_FUNCTIONS) \ >> && (_POSIX_THREAD_SAFE_FUNCTIONS+0 >= 0) >> Presumably aCC sets these macros incorrectly, or this code is not >> correct. Maybe the check should be for >0? They are defined in <sys/unistd.h> (but the check will fail if the header file is not included). >> Perhaps you can check what _POSIX_THREAD_SAFE_FUNCTIONS is defined to >> on aCC both with and without -mt? On Linux 2.4.21 + gcc 3.3.4, I get >> 200112 both with -pthread and without. >> >> #include <pthread.h> >> #include <iostream> >> int main () { std::cout << _POSIX_THREAD_SAFE_FUNCTIONS << >> std::endl; } It will fail in aCC if <unistd.h> is not included since -mt doesn't set these macros. >> HP isn't like MS where you need uniform >> mt or not across all translation units if you want happiness, but I >> wouldn't think you'd want to enable mt settings behind the users' back. I'm afraid its not, -mt needs to be defined consistently, otherwise there can be unexpected runtime problems. >> > Since somebody suggested that _REENTRANT is defined on HP >> when the '-mt' flag is used, what about only adding adding following to this #if >> > >> > # if defined(_POSIX_THREAD_SAFE_FUNCTIONS) \ >> > && defined(_SC_THREAD_SAFE_FUNCTIONS) \ >> > && (_POSIX_THREAD_SAFE_FUNCTIONS+0 >= 0) >> > || (defined(__HP_aCC) && defined(_REENTRANT)) >> I don't use boost build, but I thought the existing ifdef >> block seemed like it should work. I don't know much about HPUX on Itanium, but I >> went grepping on my HP 11i box, and found the >> _POSIX_THREAD_SAFE_FUNCTIONS define in /usr/include/sys/unistd.h. Right, >> Then I remembered that to use the new posix friendly APIs on 11i, you >> need a -D_POSIX_C_SOURCE=199506L. I'd bet that if you added that to >> your build, things would work a lot more nicely. I think that define >> is only contra-indicated if you're still trying to use CMA threads >> (which is not a good idea). Yes, but setting -mt will take care of it. But I don't think its needed for the check we are doing here. >> If you do end up needing a modification of the define block >> above, I'd recommend __hpux rather than __HP_aCC since this is a platform issue >> rather than a compiler issue. But, the problem is not with using g++ on HP-UX. >> > || (defined(__HP_aCC) && defined(_REENTRANT)) I presume no change is needed if it is ensured (with a #ifdef guard?) that <unistd.h> is included before the check. -Ganesh

4 7

[serialization] add_facet, VC7.1, and overloading operator new
by Chris Byrne 22 Jun '05

22 Jun '05

Hi, I've been playing around with overloading global operator new and delete and came across a problem concerning facets with VC7.1 in debug mode. Internally facets are reference counted and destroyed in [locale0.cpp - locale::_Locimp::~_Locimp()] via a macro _DELETE_CRT [xdebug]. Now when _DEBUG is defined this macro will not call 'operator delete' directly. So any facets added to a locale using 'operator new' will not be freed with 'operator delete'. In my case this leads to an assertion in dbgheap.c. This is because the heap manager correctly recognizes that it was not responsible for the allocation. boost/archive/impl/basic_text_iprimitive.ipp: add_facet( std::locale::classic(), new codecvt_null<BOOST_DEDUCED_TYPENAME IStream::char_type> ) Minimal example is appended to the bottom of this post. As for a possible work around (read hack) you can use _NEW_CRT instead of new directly. A some what nicer hack^H^H^H^Hsolution may be to get add_facet to perform the actual facet allocation itself using _NEW_CRT instead of the caller. Chris Byrne //////////////////////////////////////////////////////////////////////////// #include <boost/archive/add_facet.hpp> #include <boost/archive/codecvt_null.hpp> #include <boost/shared_ptr.hpp> #include <stdlib.h> #include <malloc.h> using namespace boost; using namespace boost::archive; using namespace std; void* operator new(size_t size) { char* block = reinterpret_cast<char*>(malloc(size + 1)); return block + 1; } void operator delete(void* address) { if (!address) return; char* block = reinterpret_cast<char*>(address); free(block - 1); } int main() { shared_ptr<locale> p; p.reset( add_facet(locale::classic(), new codecvt_null<char>) // add_facet(locale::classic(), _NEW_CRT codecvt_null<char>) ); p.reset(); return 0; }

2 2