- Boost - lists.boost.org

[SoC] project ideas: BigInt
by Andrew Sutton 11 Mar '10

11 Mar '10

I put BigInt back on the project ideas board with a caveat that some approaches aren't viable due to licensing concerns and that successful proposals should include discussion of those concerns. Out of curiosity, do we have a summary of those licensing issues and other concerns for this project? I haven't had the time to dig through archives. If we're accepting for BigInt, should also solicit a project for arbitrary precision floats? What about a fixed point data structure? Andrew Sutton andrew.n.sutton(a)gmail.com

4 6

[log] Review attempt
by Roland Bock 11 Mar '10

11 Mar '10

Hi, good to see that boost.log is being formally reviewed! From what I read in the documentation so far, I am really looking forward to seeing the library included in boost. I sure want to do some tests, hoping to replace our current logging system, soon, but today I can only answer the following review item: - Did you try to use the library? With what compiler? Did you have any problems? Yes, I tried and failed to compile it. Details are below. Platform: Ubuntu 8.04, 64bit, g++ 4.2.4 Intel QuadCore 2.5GHz, 8GB Ram Compilation: ============ Sounds embarassing, but I failed to compile the library. I copied the folders boost, lib and doc from boost-log-RC4 to boost_1_42_0, called ./bootstrap.sh ./bjam -d+2 --build-dir=build --with-log --prefix=/my/install/path link=shared runtime-link=shared install All looked well until this point: gcc.compile.c++ build/boost/bin.v2/libs/log/build/gcc-4.2.4/release/threading-multi/filter_parser.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -fno-strict-aliasing -DBOOST_ALL_NO_LIB=1 -DBOOST_DATE_TIME_DYN_LINK=1 -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_LOG_DLL -DBOOST_LOG_SETUP_BUILDING_THE_LIB=1 -DBOOST_LOG_SETUP_DLL -DBOOST_LOG_USE_NATIVE_SYSLOG=1 -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_THREAD_POSIX -DBOOST_THREAD_USE_DLL=1 -DDATE_TIME_INLINE -DNDEBUG -I"." -c -o "build/boost/bin.v2/libs/log/build/gcc-4.2.4/release/threading-multi/filter_parser.o" "libs/log/src/filter_parser.cpp" The process cc1plus was running about 20 minutes (100%CPU, moderate RAM usage) before anything else happened. Then, after lots and lots of very long error messages, it continues like this: ...skipped <pbuild/boost/bin.v2/libs/log/build/gcc-4.2.4/release/threading-multi>libboost_log.so.1.42.0 for lack of <pbuild/boost/bin.v2/libs/log/build/gcc-4.2.4/release/threading-multi>attribute_set.o... Hmm. Not sure how to proceed. Should I send the whole bunch of error messages to the list as an attachment? Regards, Roland

5 13

Summer of Code 2010
by Vladimir Prus 11 Mar '10

11 Mar '10

Folks, Google Summer of Code will continue in 2010, and I believe the organization applications will be accepted starting March 8. Are we going to participate, and if so, who is taking responsibility for submitting the application? Thanks, Volodya

15 41

[log] Boost.Log formal review
by Ralf Globisch 10 Mar '10

10 Mar '10

Firstly, thanks for the wonderfully written library Andrey. * Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Yes, definitely! The general review checklist is provided below: * What is your evaluation of the design? Good design and simple enough to use. Highly flexible and not too complex. * What is your evaluation of the implementation? Did not consider the implementation. * What is your evaluation of the documentation? Detailed documentation that details rationale, design decisions, tutorials, etc. AFAIR there was no link to the examples in the documentation, that perhaps could be added (if it isn't there already) to make it easier to get started. * What is your evaluation of the potential usefulness of the library? A logging library is a necessary debugging tool and is very useful if not neccessary in any application. A "standard" (and boost is as close to standard as it gets) logging library is long overdue. After searching extensively for a suitable logging library, I finally came across this library which satisfied all my demands. I had previously implemented my own logging library for use in a project which had specific requirements and this library met all of them and is far superior. However I should also mention that I have only recently compiled and tested the library using the provided examples as a quick guide to get going so my experience with the library is somewhat limited. * Did you try to use the library? With what compiler? Did you have any problems? Briefly, used some of the examples to get started. I would have liked to play with the library more but am submitting this review now due to limited time constraints. - Compilation: Compiled under Windows 7, Visual Studio 2008 without any problems * How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? I compiled the library and built a couple of the examples, changed parameters just to get an introductory feel. By no means an in-depth study. Read through the documentation. For me most importantly, I compared the functionality of the log library to the functional requirements of a logging library I wrote for use in a commercial real time streaming system and this library met all requirements and is far more flexible and superior to my own implementation. * Are you knowledgeable about the problem domain? Somewhat, I have written my own logging library although nowhere near as extensive as this one. Also, I am fairly new to boost (started using aspects of boost less than two years ago) and from reading through this mailing list I still have a lot to learn about c++/design, etc. From a previous post about the log library: > FWIW, I consider this library to be > http://en.wikipedia.org/wiki/Data_logging > and not the database/filesystem logging stuff, > http://en.wikipedia.org/wiki/Write_ahead_logging Agreed. This library allows one to log all application-related information in a simple manner and provides an effective debugging tool. Regards, Ralf -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support.

1 0

[SoC] [Asio] User input
by Andrew Sutton 10 Mar '10

10 Mar '10

A couple of years ago there was an SoC idea to extend Asio with user-input. This seemed like it may have been a pretty good idea. I think it would be great if, minimally, Boost provided some mechanism of interacting with a shell in raw input mode--in a well-designed and portable way, of course :) Did any work actually occur in this direction? Does it still seem like a viable SoC project? Would anybody be willing to mentor it? Andrew Sutton andrew.n.sutton(a)gmail.com

4 7

[bimap] Includes serialization headers even if BOOST_BIMAP_DISABLE_SERIALIZATION is defined
by Christian Holmquist 10 Mar '10

10 Mar '10

Hello, I noticed this issue with boost 1.42, but it might have been there for a while. Quite a few headers have #include <boost/serialization/nvp.hpp> I think the above should be guared with #ifndef BOOST_BIMAP_DISABLE_SERIALIZATION #include <boost/serialization/nvp.hpp> #endif Regards, Christian

2 2

[signals2] missing Jamfile and compile errors with VC8
by Michael Caisse 10 Mar '10

10 Mar '10

I was surprised to not find a Jamfile in the libs/signals2/example directory. Please find an example below. The reason I headed toward the examples is that I'm having trouble with this type of line and VC8: typedef boost::signals2::signal<void ()> signal_t; In fact doc_view_acm.cpp will not compile because of it. disconnect_and_block.cpp also has compilation errors. Results verified in 1.41 and 1.42 with VC8 and gcc 4.3.2 --------------------------------------------------------- # Boost.Signals2 Library project : requirements <source>/boost//headers ; exe hello_world_slot : hello_world_slot.cpp ; exe hello_world_multi_slot : hello_world_multi_slot.cpp ; exe ordering_slots : ordering_slots.cpp ; exe passing_slots : passing_slots.cpp ; exe extended_slot : extended_slot.cpp ; exe custom_combiners : custom_combiners.cpp ; exe disconnect_and_block : disconnect_and_block.cpp ; exe doc_view : doc_view.cpp ; exe doc_view_acm : doc_view_acm.cpp ; exe doc_view_acm_deconstruct : doc_view_acm_deconstruct.cpp ; exe postconstructor_ex1 : postconstructor_ex1.cpp ; exe postconstructor_ex2 : postconstructor_ex2.cpp ; exe predestructor_example : predestructor_example.cpp ; exe signal_return_value : signal_return_value.cpp ; exe slot_arguments : slot_arguments.cpp ; --------------------------------------------------------------- -- ---------------------------------- Michael Caisse Object Modeling Designs www.objectmodelingdesigns.com

2 3

[signals2] lamda placeholder collision
by Michael Caisse 10 Mar '10

10 Mar '10

I am converting some older code to use signals2. The old source uses boost.lambda which results in a collision of placeholders from bind (included by signals2) and lambda. I converted to phoenix about a year ago and I'll fix this "problem" by moving the lambdas to phoenix ... but ... what is supposed to be the correct course of action for source wanting to use both signals2 and Boost.Lambda? Regards - michael -- ---------------------------------- Michael Caisse Object Modeling Designs www.objectmodelingdesigns.com

2 2

Soc: project idea
by Michele Caini 10 Mar '10

10 Mar '10

Hi all, what about extending GIL with a watermarking framework? I'm not an expert in using GIL, however if users are able to handle images via a generic way, I think it's possible (and quite easy) to develop an infrastructure of algorithms that manage images adding watermarks. Watermarking is a know problem, today. ;-) Michele

1 0

[inspect] More changes to Inspection Report
by Beman Dawes 09 Mar '10

09 Mar '10

More changes to the Inspection Report: * Line numbers are now shown when a problem is associated with a specific line in a file. * Apple macros clashes now show the specific name causing the problem. * Spacing is optimized so that problems without line numbers don't take up so much report space. See the results at http://boost.cowic.de/rc/inspect-trunk.html Thanks to everyone who commented yesterday! --Beman

6 6