- Boost - lists.boost.org

gcc-4.3 doesn't compile polymorphic_(i)(o)archive.hpp (attn ramey)
by Steve M. Robbins 19 May '08

19 May '08

Hello, I need to fix ticket 1715 for Debian's Boost 1.35.0 packages. From the ticket, it's unclear what the final fix is. Can "ramey" confirm that it contained in these two changesets: ------------------------------------------------------------------------ r43958 | ramey | 2008-03-31 11:49:53 -0500 (Mon, 31 Mar 2008) | 1 line correction of error which prevented compilation on gcc 43 - again ------------------------------------------------------------------------ r43955 | ramey | 2008-03-31 10:46:48 -0500 (Mon, 31 Mar 2008) | 1 line Corrected error in detection of 64 bit support ------------------------------------------------------------------------ Thanks, -Steve P.S. I thought there is a way to obtain the changesets from the ticket, but I can't figure out how for this one.

1 0

[date_time] Deficiencies in the interface
by Jonathan Biggar 18 May '08

18 May '08

I found getting either of thse two bits of information to be much harder than it ought to be: 1. The default time zone for the program. 2. The time zone offset for the local_date_time clocks. -- Jon Biggar Floorboard Software jon(a)floorboard.com jon(a)biggar.org

2 3

Bjam in 1.34.1 missing g++ compile option for address-model=32
by Richard Hadsell 18 May '08

18 May '08

I am trying to build Boost for G++ 32-bit applications on an Opteron system running Linux Fedora Core 3. This is my command: bjam --user-config=user-config.LINUX_AMD32 threading=multi instruction-set=opteron address-model=32 variant=release,debug,profile --stagedir=stageA32 stage and this is in my user-config file: using gcc : 3.4.4 : /opt/gcc344/bin/g++344 : <compileflags>-fPIC <linkflags>-fPIC ; The first evidence I had is that the .so libraries want to link to 64-bit shared libraries: 12% ldd libboostrgx.so librt.so.1 => /lib64/tls/librt.so.1 (0x00002aaaaac65000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00002aaaaad7f000) libm.so.6 => /lib64/tls/libm.so.6 (0x00002aaaaaf71000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002aaaab0f8000) libpthread.so.0 => /lib64/tls/libpthread.so.0 (0x00002aaaab203000) libc.so.6 => /lib64/tls/libc.so.6 (0x00002aaaab318000) /lib64/ld-linux-x86-64.so.2 (0x0000555555554000) Then I ran the same bjam command with the option that shows the commands executed. This is typical: "/opt/gcc344/bin/g++344" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -fPIC -pthread -march=opteron -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o "bin.v2/libs/test/build/gcc-3.4.4/release/address-model-32/instruction-set-opteron/link-static/threading-multi/test_tools.o" "libs/test/src/test_tools.cpp" It recognized the other options I requested, but not 'address-model=32'. -- Dick Hadsell 914-259-6320 Fax: 914-259-6499 Reply-to: hadsell(a)blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 44 South Broadway, White Plains, NY 10601

3 9

Preliminary Review Request (2): boost-memory
by shiwei xu 17 May '08

17 May '08

What is new? 1. Lock-free free list (workarounds ABA problem). 2. Provide both region allocators (boost::auto_alloc, boost::scoped_alloc) and general-purpose allocators (boost::gc_alloc). 3. Notes: To fit for C++ exception semantics (See the example named "testExceptionSemantics"), I updated the specification of GC Allocator. Highlights: 1. Allocating memory is very fast. 2. No memory leaks. No need to delete objects manually. Or forgetting to delete objects is allowed. Thanks: * Steven Watanabe * Scott McMurray * Tim * Diduck, Lance To gain the source code, you can: 1. Svn checkout http://winx.googlecode.com/svn/tags/boost-memory-0.2.00/. 2. Svn checkout http://svn.boost.org/svn/boost/sandbox/memory/. --- What is boost-memory? It provides allocators named "GC Allocator". Note "GC Allocator" isn't GC. GC Allocator is different from STL Allocator. The following is minimum specification for GC Allocator: typedef void (*DestructorType)(void* data); concept GCAllocator { // Allocate memory without given a cleanup function void* allocate(size_t cb); // Allocate unmanaged memory with a cleanup function void* unmanaged_alloc(size_t cb, DestructorType fn); // Commit unmanaged memory to be managed. void* manage(void* p, destructor_t fn); // Deprecated: allocate memory with a cleanup function void* allocate(size_t cb, DestructorType fn) { return manage(unmanaged_alloc(cb, fn), fn); } // Cleanup and deallocate all allocated memory by this GC Allocator void clear(); // Swap two GCAllocator instances void swap(GCAllocator& o); }; For more information about GC Allocator, refer to http://www.codeproject.com/KB/cpp/gc-allocator.aspx

2 5

"Unknown compiler version"
by Vladimir Prus 17 May '08

17 May '08

Hi, quite a number of headers in boost/config/compiler have bits like this: # error "Unknown compiler version - please run the configure tests and report the results" I think this cause more hard than good these days. If a new version of an otherwise perfectly conforming compiler is released, this error will be emitted when compiling Boost. So, users would have to manually hack the config headers and keep this change locally. And, it's likely that some users won't even bother -- especially given that the message say to run some configure tests, and where those configure tests are is not clear. And definitely, those tests have nothing to do with the 'configure' script at the top-level dir. So, the message is likely to totally confuse some users, and force other users to keep local modifications to boost. Can we either remove this check, or assume that unknown version of compiler is identical in behaviour to the last known one? Thanks, Volodya

3 6

Review Request: Generalization of the Pimpl idiom
by Vladimir.Batov＠wrsa.com.au 17 May '08

17 May '08

I hope I am following the submission procedure correctly. I read the guidelines and I seem to do what is needed. Apologies if I missed something. The code is in the Boost Vault called Pimpl.zip It compiles with GCC 4.1.2 (I use it on Ubuntu 7.04) and MS Visual Studio 2005. Documentation is at DDJ site: http://www.ddj.com/cpp/205918714 Any questions/suggestions/critique - vladimir.batov(a)wrsa.com.au Thanks, Vladimir

5 7

[future] Will you provide allocators?
by vicente.botet 16 May '08

16 May '08

Hi, Both implementation of futures used at least two call to new, one for T and one for the common class between the future and the promise. Le me kno if I have missed something, do we really need the shared_ptr<T>? can't we use the future_object/future_impl class to store directly T. On the Anthony implementation we see already the intent to use allocators for the promise construction // template <class Allocator> explicit promise(Allocator a); but not for the new T in template<typename T> struct future_traits { typedef boost::scoped_ptr<T> storage_type; // ... static void init(storage_type& storage,source_reference_type t){storage.reset(new T(t));} //... } Anthony, do you plan to use the same allocator for T? Braddock, do you plan to use allocators? Best _____________________ Vicente Juan Botet Escriba

1 0

Trac internal error
by Vladimir Prus 16 May '08

16 May '08

Trying to visit: http://svn.boost.org/trac/boost/ticket/1587 results in: Traceback (most recent call last): File "/opt/trac/lib/python2.3/site-packages/trac/web/main.py", line 406, in dispatch_request dispatcher.dispatch(req) File "/opt/trac/lib/python2.3/site-packages/trac/web/main.py", line 244, in dispatch req.display(template, content_type or 'text/html') File "/opt/trac/lib/python2.3/site-packages/trac/web/api.py", line 358, in display data = self.hdf.render(template, form_token) File "/opt/trac/lib/python2.3/site-packages/trac/web/clearsilver.py", line 296, in render injector.feed(template.render()) File "/usr/lib/python2.3/HTMLParser.py", line 108, in feed self.goahead(0) File "/usr/lib/python2.3/HTMLParser.py", line 148, in goahead k = self.parse_starttag(i) File "/usr/lib/python2.3/HTMLParser.py", line 239, in parse_starttag endpos = self.check_for_whole_start_tag(i) File "/usr/lib/python2.3/HTMLParser.py", line 314, in check_for_whole_start_tag self.error("malformed start tag") File "/usr/lib/python2.3/HTMLParser.py", line 115, in error raise HTMLParseError(message, self.getpos()) HTMLParseError: malformed start tag, at line 116, column 86 Could Trac admins take care of this? This issue appears to be duplicate of 1588, so I'll be fine with any solution that makes 1587 no longer assigned to me :-) - Volodya

4 5

status of property_tree?
by Ronald Garcia 16 May '08

16 May '08

Hi, I am wondering what the status of the property_tree library is. It appears to be in SVN, and it was reviewed some time ago, but I do not see links to it from the Boost web pages. Does it appear in any boost releases or is it still pending for the next Boost release? Thanks, ron

1 0

[future] direct construct from value
by Frank Mori Hess 16 May '08

16 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've just noticed that neither Anthony's or Braddock's future libraries seem to support construction of a future directly from a value, like future<int> fut_int(5); Adding such a constructor gives support for implicit conversion of a value of type T to a future<T>. So a function which takes futures as arguments can also seamlessly accept values: future<void> my_func(future<int> f1, future<int> f2); my_func(fut_int, 3); This is important for the usability of poet::active_function, which takes all parameters as futures. - -- Frank -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFILDds5vihyNWuA4URAguzAJwIFdVharrD6w1QMq0R7H6NVV8TJgCfQ1hw MeYEoiqA5mOy0wY52n/tHE0= =6tTp -----END PGP SIGNATURE-----

3 4