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

[Serialization] load_binary/save_binary purpose
by Peter S. 31 Aug '08

31 Aug '08

Hi, I'm fairly new to boost so please excuse if my question may sound stupid :) I was wondering what the actual purpose of the load_binary/save_binary methods of the Archive concept classes is. In the documentation section "Archive Concepts", it is noted, that save_binary( u, count ) "Appends to the archive size_t(count) bytes found at u" and load_binary( u, count ) "Retrieves from la size_t(count) bytes and stores them in memory starting at u". Is this meant to a) enable appending random data after some object was serialized to the archive or is this really b) a lowlevel interface through which all data is read/written to the archive, as one could think (or at least, I did :)) by reading the "Archive Class Reference" also found in the documentation? And if case b) applies, couldn't that become a problem, when someone likes to implement an archive where it isn't quite possible to write raw binary data to as additional information is needed (databases/column names come to mind)? Thanks and bye, Peter

3 4

boost python embedder crashes
by daniel.oberhoff＠fit.fraunhofer.de 31 Aug '08

31 Aug '08

Hi, I want to embedd python into my app using boost:ython. sadly it crashes all of the time. it crashes straight on exec, but also trying to retrieve, say, the __main__ module. strangely enough using PyImport_ImportModule does not crash, even though it looks that that is just what python::import calls (where it crashes according to gdb). Has anyone else had this experience? I have taken care to move my macports build of python out of the way, so that both boost and my app just see the appe compiled python. further i get a crash also on exec on ubuntu (havent tried import there yet). -- Daniel

2 1

Re: [Boost-users] [filesystem][xpressive] Hotfix patchesavailablefor 1.36.0
by raindog＠macrohmasheen.com 31 Aug '08

31 Aug '08

I'm sorry my cell phone does not add < to every line of prior emails, that your mail client is too crappy to support a threaded view, and your brain too weak to read the giant email header immediately following my response. ------Original Message------ From: Jurko Gospodnetić Sender: boost-users-bounces(a)lists.boost.org To: boost-users(a)lists.boost.org Cc: boost(a)lists.boost.org ReplyTo: boost-users(a)lists.boost.org Sent: Aug 30, 2008 1:59 AM Subject: Re: [Boost-users] [filesystem][xpressive] Hotfix patchesavailablefor 1.36.0 Hi raindog(a)macrohmasheen.com > My 2 cents: Argh... please do not top-post... and if you do then at least do not make your part of the mail long AND not place any quoting characters in front of lines belonging to the original post you are replying to. Reading that mail was a very unpleasant experience. Many thanks. Best regards, Jurko Gospodnetić _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users Sent from my Verizon Wireless BlackBerry

1 0

Re: [Boost-users] cross-platfrom binary serialization?
by michal.x.strzelczyk＠jpmorgan.com 31 Aug '08

31 Aug '08

IMO the pragmatic approach would be to settle with one fp format and implement (more or less trivial) transformation functions to support the platforms that don't implement it natively. Picking IEEE754 standard would seem fine unless somebody can point out gaps preventing this from being able to convey features other formats can. Going further, to accommodate the somewhat rare cases where IEEE754 would not be the best choice the library could support multiple representations and platform-specific transformations between them leaving the choice of the FP format used by the archive (which could be modified at any time using manipulators) to the programmer. _ Michal Strzelczyk Daryle Walker <darylew(a)hotmail.com> Sent by: boost-users-bounces(a)lists.boost.org 28/08/2008 10:13 Please respond to boost-users(a)lists.boost.org To boost-users(a)lists.boost.org cc Subject Re: [Boost-users] cross-platfrom binary serialization? On Aug 27, 2008, at 4:38 PM, Bo Peng wrote: >> I have an alternate suggestion: what about continued fractions? >> Turn the >> floating point value into a list of integers. This works no >> matter what >> f.p. systems the source and destination use. You just need a >> portable >> integer serialization format. > > Then why cannot we use IEEE745 format for float serialization on > all systems? Because I don't think that the IEEE-754 internal format is as stable as you think it is. (Looking at Wikipedia's entries on IEEE-754 and 754r, there is a standard conceptual format, but problem is how do various implementations carry out the internal bit-wise format. Room for interpretation will doom your plan.) > 1. If a systems is IEEE745 compatible, serialize float numbers > directly. This will work 99.9% of the times, and will be very > efficient. > 2. If a system is not IEEE745 compatible, to serialize a float number, > we write the number as 32 or 64 continuous bits, in IEEE745 format, to > de-serialize a float number, we read the number in IEEE745 formats and > write in native float format. An intermediate string representation > can be used for the translations. The string or "direct" conversions may introduce rounding errors. > I mean, these continuous IEEE745 bits are equivalent to your "portable > integer serialization format", but will be much more efficient on > IEEE745 compatible systems. Is it worth potentially screwing 0.01% of your customers when you may not have to? -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users Generally, this communication is for informational purposes only and it is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. In the event you are receiving the offering materials attached below related to your interest in hedge funds or private equity, this communication may be intended as an offer or solicitation for the purchase or sale of such fund(s). All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities.

8 12

[pool] conflict with _CRTDBG_MAP_ALLOC on VS 2005
by Bob Marinier 31 Aug '08

31 Aug '08

I'm using Visual Studio 2005 SP1. If I compile a debug build with "#define _CRTDBG_MAP_ALLOC" (which is used to help track down memory leaks), then I get a lot of error messages from boost::pool (e.g., any of the example snippets in the documentation). The errors are shown below. It appears that with that symbol defined, several macros get defined in crtdbg.h, including the following: #define malloc(s) _malloc_dbg(s, _NORMAL_BLOCK, __FILE__, __LINE__) #define free(p) _free_dbg(p, _NORMAL_BLOCK) ...which I suspect is the source of the problem. Is this a pool bug, or is there something I'm supposed to #define to make this work? Thanks, Bob Marinier 1>c:\program files\boost\boost_1_35_0\boost\pool\simple_segregated_storage.hpp(99) : warning C4003: not enough actual parameters for macro 'malloc' 1>c:\program files\boost\boost_1_35_0\boost\pool\simple_segregated_storage.hpp(99) : error C2059: syntax error : ',' 1> c:\program files\boost\boost_1_35_0\boost\pool\simple_segregated_storage.hpp(161) : see reference to class template instantiation 'boost::simple_segregated_storage<SizeType>' being compiled 1>c:\program files\boost\boost_1_35_0\boost\pool\simple_segregated_storage.hpp(111) : error C2059: syntax error : 'constant' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(54) : error C2059: syntax error : 'constant' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(56) : error C2059: syntax error : 'constant' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(65) : error C2059: syntax error : 'constant' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(67) : error C2059: syntax error : 'constant' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(219) : warning C4003: not enough actual parameters for macro 'malloc' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(223) : warning C4003: not enough actual parameters for macro 'malloc' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(231) : warning C4003: not enough actual parameters for macro 'malloc' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(251) : warning C4002: too many actual parameters for macro 'free' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(219) : error C2059: syntax error : ',' 1> c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(278) : see reference to class template instantiation 'boost::pool<UserAllocator>' being compiled 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(241) : error C2059: syntax error : 'constant' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(251) : error C2059: syntax error : 'constant' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(252) : error C2535: 'void boost::pool<UserAllocator>::_free_dbg(void *const )' : member function already defined or declared 1> c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(241) : see declaration of 'boost::pool<UserAllocator>::_free_dbg' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(451) : warning C4003: not enough actual parameters for macro 'malloc' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(500) : warning C4003: not enough actual parameters for macro 'malloc' 1>c:\program files\boost\boost_1_35_0\boost\pool\singleton_pool.hpp(55) : warning C4003: not enough actual parameters for macro 'malloc' 1>c:\program files\boost\boost_1_35_0\boost\pool\singleton_pool.hpp(59) : warning C4003: not enough actual parameters for macro 'malloc' 1>c:\program files\boost\boost_1_35_0\boost\pool\singleton_pool.hpp(91) : warning C4002: too many actual parameters for macro 'free' 1>c:\program files\boost\boost_1_35_0\boost\pool\singleton_pool.hpp(95) : warning C4002: too many actual parameters for macro 'free' 1>c:\program files\boost\boost_1_35_0\boost\pool\singleton_pool.hpp(55) : error C2059: syntax error : ',' 1> c:\program files\boost\boost_1_35_0\boost\pool\singleton_pool.hpp(115) : see reference to class template instantiation 'boost::singleton_pool<Tag,RequestedSize,UserAllocator,Mutex,NextSize>' being compiled 1>c:\program files\boost\boost_1_35_0\boost\pool\singleton_pool.hpp(79) : error C2059: syntax error : 'constant' 1>c:\program files\boost\boost_1_35_0\boost\pool\singleton_pool.hpp(91) : error C2059: syntax error : 'constant' 1>c:\program files\boost\boost_1_35_0\boost\pool\singleton_pool.hpp(92) : error C2535: 'void boost::singleton_pool<Tag,RequestedSize,UserAllocator,Mutex,NextSize>::_free_dbg(void *const )' : member function already defined or declared 1> c:\program files\boost\boost_1_35_0\boost\pool\singleton_pool.hpp(79) : see declaration of 'boost::singleton_pool<Tag,RequestedSize,UserAllocator,Mutex,NextSize>::_free_dbg' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool_alloc.hpp(180) : warning C4003: not enough actual parameters for macro 'malloc' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool_alloc.hpp(194) : warning C4003: not enough actual parameters for macro 'malloc' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool_alloc.hpp(210) : warning C4002: too many actual parameters for macro 'free' 1>c:\program files\boost\boost_1_35_0\boost\pool\simple_segregated_storage.hpp(99) : error C2059: syntax error : ',' 1> c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(134) : see reference to class template instantiation 'boost::simple_segregated_storage<SizeType>' being compiled 1> with 1> [ 1> SizeType=boost::default_user_allocator_new_delete::size_type 1> ] 1> c:\program files\boost\boost_1_35_0\boost\pool\pool_alloc.hpp(50) : see reference to class template instantiation 'boost::pool<UserAllocator>' being compiled 1> with 1> [ 1> UserAllocator=boost::default_user_allocator_new_delete 1> ] 1> c:\program files\microsoft visual studio 8\vc\include\vector(416) : see reference to class template instantiation 'boost::pool_allocator<T>' being compiled 1> with 1> [ 1> T=soarxml::xmlString 1> ] 1> c:\program files\microsoft visual studio 8\vc\include\vector(426) : see reference to class template instantiation 'std::_Vector_val<_Ty,_Alloc>' being compiled 1> with 1> [ 1> _Ty=soarxml::xmlString , 1> _Alloc=boost::pool_allocator<soarxml::xmlString> 1> ] 1> c:\bob\soar-dev\soarsuite\core\elementxml\include\elementxmlimpl.h(69) : see reference to class template instantiation 'std::vector<_Ty,_Ax>' being compiled 1> with 1> [ 1> _Ty=soarxml::xmlString, 1> _Ax=boost::pool_allocator<soarxml::xmlString> 1> ] 1>c:\program files\boost\boost_1_35_0\boost\pool\simple_segregated_storage.hpp(111) : error C2059: syntax error : 'constant' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(219) : error C2059: syntax error : ',' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(241) : error C2059: syntax error : 'constant' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(251) : error C2059: syntax error : 'constant' 1>c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(252) : error C2535: 'void boost::pool<UserAllocator>::_free_dbg(void *const )' : member function already defined or declared 1> with 1> [ 1> UserAllocator=boost::default_user_allocator_new_delete 1> ] 1> c:\program files\boost\boost_1_35_0\boost\pool\pool.hpp(241) : see declaration of 'boost::pool<UserAllocator>::_free_dbg' 1> with 1> [ 1> UserAllocator=boost::default_user_allocator_new_delete 1> ]

1 0

runtime lists vs compiletime lists
by Hicham Mouline 30 Aug '08

30 Aug '08

Hello, i have 2 choices: 1) runtime class BaseD class D1 .... D200 derived from BaseD (all of them singletons, don't really store any data in them, they just provide policy) and class C1... C100 (also all derived from BaseC) for each Cxxx, there is a perferred D to deal with it, but "some" other Ds work also... the library user creates instances of Cxxx, I could then have a global runtime std::map<BaseC&, BaseD&>, that stores singletons of Cxxx, and preferred Dxxx 2) compiletime or i could store this mpl::map<> to associate each type Cxxx with its favorite Dxxx i suppose i could construct this by extending in each header file (for each Cxxx), the mpl::map with the Cxxx and its associated Dxxx Any comments are appreciated re this choice, for e.g. the max number of elts for map<> regards,

2 1

Compiling with a different version of a compiler
by Sean Farrow 30 Aug '08

30 Aug '08

Hi: Is there a way of compiling with a different version of a compiler. I.e specifying a path on the command line or two command-line in the .jam file. Chers Sean. __________ Information from ESET NOD32 Antivirus, version of virus signature database 3374 (20080821) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

2 1

Linking problem with boost ::function
by Kim Kuen Tang 30 Aug '08

30 Aug '08

Hi all, i've got linking problem (both in visual studio 2005 and 2008 in vista and boost 1.36) with this piece of code. boost::function<double (double)>h=boost::bind(std::multiplies<double>(),boost::lambda::_1,5.0); If i now write std::cout<<h(3.0) the compilation fails with the following error: visual studio 2005: error LNK2001: Nicht aufgelöstes externes Symbol ""void __cdecl boost::assertion_failed(char const *,char const *,char const *,long)" (?assertion_failed@boost@@YAXPBD00J@Z)" and visual studio 2008: error LNK2001: unresolved external symbol "void __cdecl boost::assertion_failed(char const *,char const *,char const *,long)" (?assertion_failed@boost@@YAXPBD00J@Z) But compilation is ok. with regards, Kim Tang

1 1

extening variant<> types to more than 20
by Hicham Mouline 30 Aug '08

30 Aug '08

Hello, how can one make variants over mpl sequences with over 20 types? i tried to redefine BOOST_VARIANT_LIMIT_TYPES to 21 for e.g. without success, regards,

2 1

[function] function_equal or function::operator== ambiguous overload?
by Hajo Kirchhoff 30 Aug '08

30 Aug '08

Hello, I would like to compare two boost::function<void()> objects, but get an "boost::operator ==' : 4 overloads have similar conversions" error. On Visual Studio 2008 SP1, both Win32 and x64 target platform, the following code does not compile: boost::function<void()> one, two; if (one==two) one.clear(); I get the compile error messages below. Any ideas, any help? Regards and thank you in advance Hajo 1>c:\users\hajo kirchhoff\desktop\prj\cct2_2005\r3000trunk\v4\wbr_backend\basic_stream_connector.cpp(31) : error C2666: 'boost::operator ==' : 4 overloads have similar conversions 1> c:\users\hajo kirchhoff\desktop\prj\boost\boost_1_36_0\boost\function\function_template.hpp(821): could be 'void boost::operator ==<R>(const boost::function0<R> &,const boost::function0<R> &)' [found using argument-dependent lookup] 1> with 1> [ 1> R=void 1> ] 1> c:\users\hajo kirchhoff\desktop\prj\boost\boost_1_36_0\boost\function\function_base.hpp(747): or 'bool boost::operator ==<boost::function<Signature>>(Functor,const boost::function_base &)' [found using argument-dependent lookup] 1> with 1> [ 1> Signature=void (void), 1> Functor=boost::function<void (void)> 1> ] 1> c:\users\hajo kirchhoff\desktop\prj\boost\boost_1_36_0\boost\function\function_base.hpp(738): or 'bool boost::operator ==<boost::function<Signature>>(const boost::function_base &,Functor)' [found using argument-dependent lookup] 1> with 1> [ 1> Signature=void (void), 1> Functor=boost::function<void (void)> 1> ] 1> or 'built-in C++ operator==(void (__thiscall boost::function0<R>::dummy::* )(void), void (__thiscall boost::function0<R>::dummy::* )(void))' 1> with 1> [ 1> R=void 1> ] 1> while trying to match the argument list '(boost::function<Signature>, boost::function<Signature>)' 1> with 1> [ 1> Signature=void (void) 1> ]

2 1