- Boost-users - lists.preview.boost.org

[program_options] split_winmain
by Vitaly Grechko 03 Dec '08

03 Dec '08

>Vitaly Grechko wrote: >> Could _WIN32 be removed from program_options\parsers.hpp? There is no way in >> UNIX to parse command line independently from string. To use the library I >> had to dublicate parsers.hpp and winmain.cpp files localy with _WIN32 >> removed, which is ugly. Before this I tryed to define _WIN32 before >> including parsers.hpp and undef after - this affected other boost headers >> and did not compile. >> I don't see the reason to have _WIN32 macro there because the code is just >> an algorithm and complied successfuly in all platforms. The meaning of the >> algorithm is in the name of the function 'split_winmain(...)'. >> The use case example: command lines from Windows client machines go to Unix >> server for validation and logging. In this case split_winmain is regularly >> used on UNIX >What 'validation and logging' can be possibly done on Linux, given Windows command >line? Why do you need to actually tokenize it? >- Volodya (Sorry for broken thread, It is my first message and I was a digest user and Gmane does not contain my message) Command lines can be sent by network from Windows to Linux program which processes it and send back some result (client/server system). But this is just a straightforward example. Other example: There is a tool that is compiled on Windows and Linux. It does not have argc, argv because command line is entered say in editbox. The tool should parse this line and the algorithm should be the same in all operating systems to have single behavior. In my case the user specifies a command line as an argument to a function in script file. Probably it is safe to allow using split_winmain in UNIX to avoid the hell described in previous message.

2 3

path separator char/string
by boost001 03 Dec '08

03 Dec '08

I need to get the char or string represent current system's path separator. In ACE , we can get from this constant: ACE_DIRECTORY_SEPARATOR_CHAR. Does Boost has the similar constant to do the same? I looked at the path.hpp. I think maybe I can get it from the following existing code: 1. template<class Path> struct slash { BOOST_STATIC_CONSTANT( char, value = '/' ); }; 2. # ifdef BOOST_WINDOWS_PATH template<class Path> struct path_alt_separator { BOOST_STATIC_CONSTANT( char, value = '\\' ); }; # endif 3. template<class Path> inline bool is_separator( typename Path::string_type::value_type c ) { return c == slash<Path>::value # ifdef BOOST_WINDOWS_PATH || c == path_alt_separator<Path>::value # endif ; } But I don't know exactly how. Anybody can help me? -- View this message in context: http://www.nabble.com/path-separator-char-string-tp20820786p20820786.html Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

[boost][serialization] void_upcast is very slow
by Jacob 03 Dec '08

03 Dec '08

The original "inline void_upcast" method checks if the pointer to the object is of the right type, by traversing its parents. This is necessary when using multiple inheritance, since in such a case the adress of the pointer to the object can vary depending on which base class it is cast to. While profiling one of my projects I noticed that most of the time was spent in the void_upcast method. I modified the method to return the pointer directly(see below), resulting in a high performance increase. This "solution" is possible if you avoid multiple inheritance all together, which I did. In my particular project I experienced a 75% speed increase implementing this, going from about 10 seconds to 2.5 seconds. Would it be possible to implement some functionality to turn on and off the upcasting for given classes, kind of like the tracking of objects is currently administrated? Modified "inline void_upcast": /inline void * void_upcast( extended_type_info const & derived, extended_type_info const & base, void * const t ){ return const_cast<void*>(t); }/ Yours sincerely, Jacob Holm

2 1

[FILESYSTEM]:Link problem
by Ken zhang 03 Dec '08

03 Dec '08

Hi Dear all I can't link my program with boost::filesystem, the compiler report error below: ..\binaries\lib\libresourcemanager_d.a(resimg.o):resimg.cpp:(.text$_ZN5boost10filesystem6existsINS0_10basic_pathISbIwSt11char_traitsIwESaIwEENS0_12wpath_traitsEEEEENS_9enable_ifINS0_13is_basic_pathIT_EEbE4typeERKSB_[boost::enable_if<boost::filesystem::is_basic_path<boost::filesystem::basic_path<std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >, boost::filesystem::wpath_traits> >, bool>::type boost::filesystem::exists<boost::filesystem::basic_path<std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >, boost::filesystem::wpath_traits> >(boost::filesystem::basic_path<std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >, boost::filesystem::wpath_traits> const&)]+0x77): undefined reference to `boost::filesystem::detail::status_api(std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&, boost::system::error_code&)' ..\binaries\lib\libresourcemanager_d.a(resimg.o):resimg.cpp:(.text$_ZN5boost10filesystem6detail10path_proxyERKSbIwSt11char_traitsIwESaIwEESt13_Ios_Openmode[boost::filesystem::detail::path_proxy(std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&, std::_Ios_Openmode)]+0xa8): undefined reference to `boost::filesystem::detail::create_file_api(std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&, std::_Ios_Openmode)' ..\binaries\lib\libresourcemanager_d.a(resimg.o):resimg.cpp:(.text$_ZN5boost10filesystem6detail10path_proxyERKSbIwSt11char_traitsIwESaIwEESt13_Ios_Openmode[boost::filesystem::detail::path_proxy(std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&, std::_Ios_Openmode)]+0x143): undefined reference to `boost::filesystem::detail::narrow_path_api(std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&)' ..\binaries\lib\libresourcemanager_d.a(resimg.o):resimg.cpp:(.text$_ZN5boost10filesystem6detail10path_proxyERKSbIwSt11char_traitsIwESaIwEESt13_Ios_Openmode[boost::filesystem::detail::path_proxy(std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&, std::_Ios_Openmode)]+0x1f8): undefined reference to `boost::filesystem::detail::remove_api(std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&)' ..\binaries\lib\libresourcemanager_d.a(resimg.o):resimg.cpp:(.text$_ZN5boost10filesystem9file_sizeINS0_10basic_pathISbIwSt11char_traitsIwESaIwEENS0_12wpath_traitsEEEEENS_9enable_ifINS0_13is_basic_pathIT_EEyE4typeERKSB_[boost::enable_if<boost::filesystem::is_basic_path<boost::filesystem::basic_path<std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >, boost::filesystem::wpath_traits> >, unsigned long long>::type boost::filesystem::file_size<boost::filesystem::basic_path<std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >, boost::filesystem::wpath_traits> >(boost::filesystem::basic_path<std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >, boost::filesystem::wpath_traits> const&)]+0x6b): undefined reference to `boost::filesystem::detail::file_size_api(std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&)' My boost version: 1.37 build script: bjam toolset=gcc --build-type=minimal link=shared stage Mingw32:tdm-mingw-1.808.3-f2 GCC:gcc version 4.3.2 (4.3.2-tdm-1 for MinGW) boost_system-mgw43-mt-1_37.lib boost_iostreams-mgw43-mt-1_37.lib boost_filesystem-mgw43-mt-1_37.lib The same code worked fine on VC2008. Best regards Ken

4 5

[Threads] error building 1.37.0 on cygwin with g++ 4.3.2
by frederic.bron＠alcan.com 03 Dec '08

03 Dec '08

I tried to build 1.37.0 with g++ 4.3.2 on cygwin. Got the following error. Is there a workaround for this or should I go back to g++ 3.4.4? Regards, F. Bron "g++-4" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -DBOOST_POSIX_API -DBOOST_POSIX_PATH -mfpmath=sse -march=pentium-m -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_THREAD_BUILD_LIB=1 -DBOOST_THREAD_POSIX -DNDEBUG -I"." -c -o "bin.v2\libs\thread\build\gcc-4.3.2\release\link-static\threading-multi\exceptions.o" "libs\thread\src\pthread\exceptions.cpp" In file included from ./boost/thread/detail/platform.hpp:17, from ./boost/thread/detail/config.hpp:20, from libs\thread\src\pthread\exceptions.cpp:7: ./boost/config/requires_threads.hpp:29:4: error: #error "Threading support unavaliable: it has been explicitly disabled with BOOST_DISABLE_THREADS" ...failed gcc.compile.c++ bin.v2/libs/thread/build/gcc-4.3.2/release/link-static/threading-multi/exceptions.o... gcc.compile.c++ bin.v2/libs/thread/build/gcc-4.3.2/release/link-static/threading-multi/once.o "g++-4" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -DBOOST_POSIX_API -DBOOST_POSIX_PATH -mfpmath=sse -march=pentium-m -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_THREAD_BUILD_LIB=1 -DBOOST_THREAD_POSIX -DNDEBUG -I"." -c -o "bin.v2\libs\thread\build\gcc-4.3.2\release\link-static\threading-multi\once.o" "libs\thread\src\pthread\once.cpp" In file included from ./boost/thread/detail/platform.hpp:17, from ./boost/thread/once.hpp:12, from libs\thread\src\pthread\once.cpp:7: ./boost/config/requires_threads.hpp:29:4: error: #error "Threading support unavaliable: it has been explicitly disabled with BOOST_DISABLE_THREADS" ...failed gcc.compile.c++ bin.v2/libs/thread/build/gcc-4.3.2/release/link-static/threading-multi/once.o... gcc.compile.c++ bin.v2/libs/thread/build/gcc-4.3.2/release/link-static/threading-multi/thread.o "g++-4" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -DBOOST_POSIX_API -DBOOST_POSIX_PATH -mfpmath=sse -march=pentium-m -mthreads -DBOOST_ALL_NO_LIB=1 -DBOOST_THREAD_BUILD_LIB=1 -DBOOST_THREAD_POSIX -DNDEBUG -I"." -c -o "bin.v2\libs\thread\build\gcc-4.3.2\release\link-static\threading-multi\thread.o" "libs\thread\src\pthread\thread.cpp" In file included from ./boost/thread/detail/platform.hpp:17, from ./boost/thread/detail/config.hpp:20, from libs\thread\src\pthread\thread.cpp:8: ./boost/config/requires_threads.hpp:29:4: error: #error "Threading support unavaliable: it has been explicitly disabled with BOOST_DISABLE_THREADS" libs\thread\src\pthread\thread.cpp: In function 'void boost::this_thread::sleep(const boost::system_time&)': libs\thread\src\pthread\thread.cpp:354: error: 'to_timespec_duration' was not declared in this scope ...failed gcc.compile.c++ bin.v2/libs/thread/build/gcc-4.3.2/release/link-static/threading-multi/thread.o... ...skipped <pbin.v2/libs/thread/build/gcc-4.3.2/release/link-static/threading-multi>libboost_thread-mt.a(clean) for lack of <pbin.v2/libs/thread/build/gcc-4.3.2 /release/link-static/threading-multi>thread.o... ...skipped <pbin.v2/libs/thread/build/gcc-4.3.2/release/link-static/threading-multi>libboost_thread-mt.a for lack of <pbin.v2/libs/thread/build/gcc-4.3.2 /release/link-static/threading-multi>thread.o... ...skipped <p/cygdrive/d/Softs/boost_cyg/lib>libboost_thread-mt.a for lack of <pbin.v2/libs/thread/build/gcc-4.3.2/release/link-static/threading-multi>libboost_thread-mt.a... Avis : Ce message et toute pièce jointe sont la propriété d'Alcan et sont destinés seulement aux personnes ou à l'entité à qui le message est adressé. Si vous avez reçu ce message par erreur, veuillez le détruire et en aviser l'expéditeur par courriel. Si vous n'êtes pas le destinataire du message, vous n'êtes pas autorisé à utiliser, à copier ou à divulguer le contenu du message ou ses pièces jointes en tout ou en partie. Notice: This message and any attachments are the property of Alcan and are intended solely for the named recipients or entity to whom this message is addressed. If you have received this message in error please inform the sender via e-mail and destroy the message. If you are not the intended recipient you are not allowed to use, copy or disclose the contents or attachments in whole or in part.

2 1

Re: [Boost-users] Turn off versioning in Serialization
by Brian Nantz 03 Dec '08

03 Dec '08

Robert, Thanks for the quick reply. I was able to turn all the headers off but there is still one number (which seems to be thre string length) that I can not turn off. If this is unable to be turned off then I will proceed to the Case Study you mentioned. Brian Brian Nantz wrote: > I am using serialization split member (save & load) and it works > great. I am using a text archive, but I do not want the framework to > put the "version header" in the string (e.g. 22 > serialization::archive 4 1303 ). This is the serialization library version. When you create the archive you can specify the flag no_header to suppress it. I want to simply serialize the > string and handle the versioning myself in the load function. Is > there a way to turn this off? THis sounds like your talking about class version - which is different from the above. this can be suppressed on a class by class basis. in the documentation Reference Serializable Concept Class Serialization Traits Implementation level. > If not, where can I find detailed documentation on implementing a > custom archive or build in another type of serialization (other than > binary and xml nvp)? I have looked through mailing lists and > documentation but I don't see a detailed description of how to extend > the design. Try looking at Case Studies Derivation from an existing archive cass > > Brian Robert Ramey

1 0

Problem on Boost using stlport4 on Sun C++
by a_disabatino 03 Dec '08

03 Dec '08

Hi everybody, please help me, I tried to use boost 1.34.1 and 1.36.0 same problems, I got this error: 1/boost/array.hpp", line 75: Error: Too few arguments for template std::reverse_iterator<boost::T*>. boost/boost_1_34_1/boost/array.hpp", line 289: Where: While specializing "boost::array<boost::T, boost::N>". boost/boost_1_34_1/boost/array.hpp", line 289: Where: Specialized in non-template code. /boost/boost_1_34_1/boost/array.hpp", line 76: Error: Too few arguments for template std::reverse_iterator<const boost::T*>. boost/boost_1_34_1/boost/array.hpp", line 289: Where: While specializing "boost::array<boost::T, boost::N>". boost/boost_1_34_1/boost/array.hpp", line 289: Where: Specialized in non-template code. "/opt/SUNWspro/prod/include/CC/Cstd/./iosfwd", line 148: Information: Library has instance std::ostringstream::basic_ostringstream(int). "/opt/SUNWspro/prod/include/CC/Cstd/./ostream", line 471: Information: Library has instance std::operator<<(std::ostream &, const char*). "/opt/SUNWspro/prod/include/CC/Cstd/./iosfwd", line 145: Information: Library has instance std::ostream::operator<<(unsigned). "/opt/SUNWspro/prod/include/CC/Cstd/./iosfwd", line 148: Information: Library has instance std::ostringstream::str() const. "/opt/SUNWspro/prod/include/CC/Cstd/./string", line 858: Information: Library has instance std::string::basic_string(const char*, const std::allocator<char>&). if I compile Boost using the flag -library=stlport4 i was able to solve that problem, but my applications uses libCstd Sun standard library since when I tried to link the library into my application I got core. So I'd like to compile boost just using libCstd I mean sun implementation. do you have some suggests on thi issue please? you welcome Tony

2 1

Re: [Boost-users] [review][constrained_value] Review of Constrained Value Library begins today
by Jesse Perla 03 Dec '08

03 Dec '08

As someone who was about to try to write something similar out of necessity, let me throw out a few practical considerations and a use case. These are a wish list from a library user that is not a generic library programmer: What I really want is to have a "type" that contains bounds information, rather than for bounds checking itself (which is gravy). And I want to use this for pretty functional programming, and see this as an incredibly useful library and integral to taking C++ to the next level for programming mathematics. I do not see this as primarily an equivalence to units, though I understand that use case. My primary cases for this are: 1. For functors that contain domain/range sets to match the blackboard mathematics I am implementing in code. Including "operators" that map functors to functors (my main case being a derivative operator or a conditional expectation). 2. To use this an optimizer framework. The problem is that you end up having to keep around lists of reasonable bounds on what values the optimizer should be allowed to use. But this information becomes separated from the real "type" of the variable, even though that is where it conceptually belongs. And when you call optimizers you need to have both. Of course, this optimizer/root finder problem is really the same issue as maintaining range/domain for functors. So a few comments on what I would love to be able to do to support this: 1. The closed/open bounds in here is necessary, especially for optimizers where you frequently have asymptotes at the bounds (virtually always in the dynamic programming for economics problems I work with). 2. I would go further than saying that the closed/open bounds is a starting point and that the library should ultimately be designed to accomodate (runtime) unions of intervals and discrete points i.e. [x,x] in intervals. This would be very useful for game theory applications where you could get non-connected sets of equilibrium conditions. Or functions where you can have asymptotes in the middle that are not defined, but it is defined on both sides. Last, would be nice to allow for a discrete set of real values as bounds. If the design of the library could support this (maybe by returning an iterator over the ranges if necessary?) then it could be implemented later. Keep in mind that my need is to access/set the bounds at runtime rather than just boundschecking by writing my own bounds checking predicate. 3. Turning off the bounds-checking at runtime could be useful (though certinaly not through NDEBUG!), but you would NEVER want to turn off the availability of the bounds information at runtime since that is the core usefulness of the library. 4. If it is true in general, then this statement: http://student.agh.edu.pl/~kawulak/constrained_value/constrained_value/rati… makes this library practically useless. I understand the rationale, but since all optimizers take floats or doubles, and 99% of functions map doubles to doubles for me, this is an unreasonable constraint. If the problem here is just for the bounds checking, then I am not worried since I really want type information. 5. Sometimes you want to have compile-time fixed bounds , other times modifiable at runtime. So I like this, but they need to behave the same way. But what I really want to do is change the bounds of the type itself at runtime, not just the bounds on an individual instantiation. See the following to see if I am misundertanding the library: typedef bounded<double> interest_rate; interest_rate r1, r2; change_bounds(r1, .8, .99); Now the interest rate bounds on r2 don't exist, right? This is a big problem for me... It would mean that the bounds information is not kept on the type, but on the instantiation... this has extra data and has completely different semantics from the static bounds case where it really is associated with the type. What I would really want is some kind of static data associated with the type. I understand the difficulty here, but nevertheless this is the main usefulness of the library. I also note that this means the "typedef" approach may be a problem as it is set up since the library would have no way to tell the difference between these types to store static bounds, even though this is exactly what I want.: typedef bounded<double> interest_rate; typedef bounded<double> risk_aversion; interest_rate r; risk_aversion crra ; change_bounds(r, .8. .99); //Storing this statically change_bounds(crra, 1.0, 10.0); //Statically. interest_rate r_guess; //Want the right bounds! Can't exist here? Of course, with static bounds this kind of thing works. Perhaps it is reasonable to throw in some sort of useless trick for the compiler to separate when storing static data to keep semantics with the static bounds the same? I don't know if this is a good approach, but it would be reasonable to ask of library users: typedef bounded<double, "INTEREST RATE"> interest_rate; //In fact, I wouldn't even mind having the "name" available at runtime for pretty_printing... typedef bounded<double, "RISK_AVERSION"> risk_aversion; interest_rate r; risk_aversion crra ; change_bounds(r, .8. .99); //Storing this statically, now the two types are distinct? change_bounds(crra, .5, 10); //Statically. interest_rate r_guess; //Want the right bounds. Naturally, there are other cases where you might want to change the bounds on an instantiation. If both could be supported (and returned through the same bounds function, modified through different ones) that would be nice, but the above use case is far more important to me. 6) Is there any way to get the library to compile: std::max(2, i) instead of using i.value() as mentioned in the tutorial for a constrained i? This really is essential to make the library equivalent to normal operations, but with extra type information. Again, I am willing to forgo ease of use on the bounds checking for this... What I really want is the instantiation to behave EXACTLY the same as an underlying type. So overloading the ++, +, etc. are useful, but I would go further to say that perhaps everything could be done by just going back to the underlying type... with abolutely no overhead since it would make this useless for numeric programming. If I multiply or add these kinds of values, I would want the result to be of the underlying type and don't care about the mechanics of ensuring that the result type is bounded itself, etc. I can construct my own bounded type for the return type if I have to... Thanks for listening. And if people have better ideas of a framework or approach to do this kind of stuff, please tell me. I may be stretching the expectations of this library... -Jesse

1 0

[Thread] barrier destruction after wait() results in assertion
by Peter Klotz 03 Dec '08

03 Dec '08

Boost 1.37.0, Red Hat Enterprise Linux 5 x86_64, gcc 4.1: The following simple test establishes a barrier with thread count 2. One of the threads destroys the barrier after returning from wait(). This results in sporadic assertions from ~mutex(). boost/thread/pthread/mutex.hpp:45: boost::mutex::~mutex(): Assertion `!pthread_mutex_destroy(&m)' failed. #1 0x00000038306295d6 in __assert_fail () from /lib64/libc.so.6 #2 0x000000000040245a in ~mutex (this=0x1f63f010) at boost/thread/pthread/mutex.hpp:45 #3 0x0000000000402488 in ~barrier (this=0x1f63f010) at boost/thread/barrier.hpp:24 I assume that this usage of barrier is not supported/allowed. One cannot assume that the barrier can be destroyed just because the corresponding thread returned from wait(). Is this conclusion correct? Regards, Peter. #include <boost/scoped_ptr.hpp> #include <boost/thread/barrier.hpp> #include <boost/thread/thread.hpp> boost::scoped_ptr<boost::barrier> barrier; void f() { barrier->wait(); } int main(void) { barrier.reset(new boost::barrier(2)); boost::thread thread(boost::bind(&f)); barrier->wait(); barrier.reset(); thread.join(); return 0; }

3 4

Threads - Access in invalid memory Boost 1.36.0 BCB 5.8.3
by Stephen Kierzewski 03 Dec '08

03 Dec '08

Hello, I have a simple OpenGL program that is using Boost Threads and I had it working fine under Boost 1.34. I have switched to 1.36 for some of the newer mutex locking functionality and everything works fine, but.. I keep getting an invalid memory access error. My program will run fine if i skip past the offending call. Wondering if anyone has any ideas? The offending call happens when the rendering thread is created. The call stack is as follows: Access in invalid memory in process: solarsystemT.exe(4056) - :\development\boost_1_36_0\boost/thread/win32/once.hpp#125 Attempt to access 4 byte(s) at 0x00417084. 0x00411056 - E:\development\boost_1_36_0\boost/thread/win32/once.hpp#125 0x0041137B - E:\development\boost_1_36_0\libs\thread\src\win32\thread.cpp#44 0x00411A61 - E:\development\boost_1_36_0\libs\thread\src\win32\thread.cpp#151 The memory that boost::call_once is accessing is current_thread_tls_init_flag created earlier by boost::once_flag current_thread_tls_init_flag=BOOST_ONCE_INIT; I can see that this flag was created and initialized to zero. Thank you for any insight. Stephen Kierzewski

2 1