- Boost - lists.boost.org

Defect in tools/common/time_string.hpp
by Gennaro Prota 31 May '07

31 May '07

{ Last attempt to sent this: I mailed Beman, than Rene, to no avail; then, I re-subscribed to the list, went to all the confirm-that-you-exist hassle and posted, but still the message didn't appear. Sorry but I don't know what else to do. } On Sat, 26 May 2007 13:33:14 +0200, Gennaro Prota wrote: >Hi Rene, > >I sent this to Beman a while ago but he's likely too busy with >standardization: I noticed a bug in >boost/tools/common/time_string.hpp; I copied the default argument "%X >UTC, %A %d %B %Y" from the original code by him and you can see for >yourself that "UTC" in there is quite wrong. Incredibly, this problem >has been there since the beginning, and I was so stupid as to not >check the string myself. -- Genny -- Gennaro Prota -- C++ Developer, For Hire https://sourceforge.net/projects/breeze/

1 1

Any libraries now not under the Boost Software License?
by David Abrahams 31 May '07

31 May '07

http://boost.org/more/license_info.html says: Currently, some Boost libraries have their own licenses. The hope is ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ that eventually all Boost libraries will be covered by the Boost Software License. In the meantime, all libraries comply with the Boost License requirements. Is that still true now that we have Threads under the BSL? -- Dave Abrahams Boost Consulting http://www.boost-consulting.com

11 24

Interest from BoostCon
by Preston A. Elder 31 May '07

31 May '07

Hey, There was some interest in some code I had written a long time ago expressed at BoostCon - I believe I linked this before, but the location has changed. Specifically these are libraries inside of Mantra. These have not been modified in 2 years, so I wanted to know if there was any interest in them (and as such cause for me to update and submit them). If nobody is interested in them I will probably drop them, if people are interested I can look into cleaning them up and submitting. - boost::unformat - a logical reversal of boost::format (ie. scanf for boost::format): http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/include/mantra… Right now this only unformats into strings, and is not extensively tested, but it DOES work. If there is interest I will enhance it to unformat int a tuple, or something else (suggestions)? - Intrusive Tracing - the ability to activate various levels/styles of code-based tracing at runtime, and by logical code 'section'. http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/include/mantra… and http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/src/core/trace… It uses macros - and I would like to expand it to more and better tracing capabilities, but what is there works and is VERY convenient. It even supports a 'transactional' mode of tracing, to avoid trace cross-talk. Tracing can be completely compiled away for production code. - Extension to program_options to allow for more robust checking of provided values. http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/include/mantra… Some of this functionality has been put into program_options, but not as nice as I'd like it (at least last I looked at it). This allows you to do things like validate the value provided (must match this regex, must fall within this range, must pass this check function). It also allows for more advanced things like value mapping (user uses value of 'INFO', which gets mapped to the enum LogLevel_t::INFO or whatever). It also allows 'chained' checks. This is probably showing its age though, there have been certain enhancements to program_options that makes some of the stuff here unnecessary. - Date/Time and Duration formatting (both to and from) functions: http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/include/mantra… These were written before the date/time facets - but they are still useful. - Guarenteed event mechanism: http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/include/mantra… and http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/src/service/ev… This handles its own thread pool (ie. minimum number of standby threads), and operates in such a way that it will guarentee an event is started EXACTLY when you want it, even if it has to spawn a new thread to do so. - In-process watchdog: http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/include/mantra… and http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/src/service/wa… Relatively simple, but saves everyone else writing one :) - Various dispatching methodologies: http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/include/mantra… http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/include/mantra… http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/include/mantra… http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/include/mantra… These are message queues for different purposes. Each (except OTS) is backed by a thread pool that can resize based on high/low water marks. * MessageQueue - Single queue for a pool of threads. * ITS_MessageQueue - Implements a 'queue per thread' (with a 'transport' thread) to reduce lock contention by delivering messages to a worker thread for processing in bulk (includes 'fair' queueing). * Routed_MessageQueue - Adds a key to the message, guarenteeing that only one thread can process messages for a single key at any one time. - OTS_MessageQueue - Reverses ITS_MessageQueue, made for the 'other' side, ie. multiple threads sending data to a single thread (eg. a store and forward thread or something). In this case it only has a single thread (plus a collector), and has a queue per thread that PUSH's onto it instead. - Networking Stuff: http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/include/mantra… and http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/src/net Written before ASIO was accepted - probably not required anymore, but it IS a simpler approach (ie. 3 classes, thats it). Supports select, poll and epoll. - Generic Data Storage Backend: http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/include/mantra… and http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/src/storage This allows you to have a common interface to your storage back end, regardless of whether its an SQL database, Berkeley DB, XML file, etc. It also allows you to CODE a query, eg: Condition<C_LessThan>("col1", 3") && (Condition<C_EqualTo>("col2", "hello") || Condition<C_EqualTo>("col2", "world")) && Condition<C_Masked>("col3", FLAG_A | FLAG_B) This will then expand to an SQL expression for SQL DB's, or apply to data rows for non-SQL DB's - ie. it will work for all data sources. Right now I plan on re-writing this anyway to support: * Cross-table/database queries, better column limits and more operations: (http://www.neuromancy.net/mantra/trac/ticket/1) * Transactions & Cursors (http://www.neuromancy.net/mantra/trac/ticket/2) * An Object-based model (http://www.neuromancy.net/mantra/trac/ticket/3) But I would like to know if there is interest for this in the boost community or more specifically, in turning it into a boost module in its own right. - Store and Forward and Disk-Overflow: http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/include/mantra… and http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/src/file/saf.c… and http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/include/mantra… and http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/src/file/fileb… The SAF mechanism is there to implement guarenteed delivery of data, even if your application crashes. The FileBuffer provides disk-based overflow for memory-constrained situations (eg. where you have a socket, and you can get massive bursts of data to go out the socket, but cannot send it as fast as the burst - especially where you have thousands of such bursty connections). - Python bindings for some boost libraries: http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/python/boost Right now I have bindings for boost::format, date_time and tribool. There was interest in these but nowhere to put them. In addition they need updating (especially date_time). I also plan on re-writing my Logging library: http://www.neuromancy.net/mantra/trac/browser/trunk/Mantra-I/include/mantra… to be MUCH more efficient and flexible with regards to adding new logging back ends and formatting (http://www.neuromancy.net/mantra/trac/ticket/4) Sorry for the length of this post. Please let me know if you think some of these things would look good with a boost:: prefix :) PreZ :) BTW - I enjoyed BoostCon immensely, thanks again to the organizers and I enjoyed meeting many of you. This is an email you can contact me at :)

6 9

[uuid] - error in function operator>>()
by Oliver.Kowalke＠qimonda.com 31 May '07

31 May '07

Hello, I get following error from uuid v8 library: /opt/boost/include/boost-1_34/boost/uuid.hpp:209: instantiated from void boost::uuid::construct(const std::basic_string<_CharT, _Traits, _Alloc>&) [with ch = char, char_traits = std::char_traits<char>, alloc = std::allocator<char>] /opt/boost/include/boost-1_34/boost/uuid.hpp:76: instantiated from here /opt/boost/include/boost-1_34/boost/uuid.hpp:468: Fehler: keine passende Funktion fr Aufruf von find(char [16], char* const&, char&) // means: function not found Oliver

1 0

lexical_cast error with double?
by Preston A. Elder 31 May '07

31 May '07

This may have been posted before, but I did not see it or the solution. This code: double d = 72.35 std::string = boost::lexical_cast<std::string>(d); Results in the string 72.3499999999999999999 However printf("%f\n", d); Results in 72.350000 Any reason for this - or more importantly, any way to fix it and prevent it happening again? PreZ :)

1 0

[assign] ptr_list_of legal?
by shunsuke 31 May '07

31 May '07

Hi, I found a snippet from <boost/assign/ptr_list_of.hpp>: template< class T > class generic_ptr_list { // ... public: template< class PtrContainer > operator std::auto_ptr<PtrContainer>() const { .. } }; IIRC, this automatic conversion doesn't work on any conforming compiler. The right way seems to make lvalue: 'operator std::auto_ptr<PtrContainer> & () const'. Regards, -- Shunsuke Sogame

2 4

Boost sandbox and Boost vault
by Edward Diener 31 May '07

31 May '07

I am confused by the use of the Boost sandbox and by the use of the Boost vault for uploading code in which others might be interested. What is the difference between these two ? Would it not be better to have a single area in which new code is uploaded ?

5 7

javascript in docs
by Gennadiy Rozental 31 May '07

31 May '07

How much javascript are we allowed in docs these days? It seems that Javascript started to appear here and there. Is there general guidelines on what is allowed? Gennadiy

6 8

Boost Soc 2006 and SubVersion
by Shams 31 May '07

31 May '07

Hi, Is there any chance of moving the SoC 2006 projects from: https://boost-consulting.com/trac/soc/browser/boost/soc https://boost-consulting.com/trac/soc/browser/boost/soc/2006 to the new SubVersion sandbox here: http://svn.boost.org/trac/boost/browser/sandbox/ Just like SoC 2007 Thanks Shams --

2 1

[UUID] Review results
by Hartmut Kaiser 30 May '07

30 May '07

Hi all, now, as Andy has finished his implementation (here: http://boost-consulting.com/vault/, file: uuid_v8.zip) we can move forward with the results of the review. This review has been kind of special in the sense that - it revealed some serious problems with the library to review (a license incompatibility problem and a security related problem around the random number generator scheme used), - it also spawned lots of dicussions on how to solve these problems. In the end we reached full agreement on what has to be done and Andy agreed to implement the changes. Normally, the mentioned problems would have prevented the acceptance of the library into Boost. OTOH, I think the following facts warrant not to reject the library in the first place: - The issues have already been discussed and a consensus has been reached on how to resolve the problems - Almost all reviewers found the proposed library to be incredibly useful and wanted to see the library accepted given the problems will be resolved - Andy fixed all of the significant problems in a short timeframe The final decision about the acceptance of the library will be made after a mini review of the proposed library (to be scheduled), which should concentrate on the new code presented by Andy and whether the mentioned problems have been appropriately fixed. Regards Hartmut Review Manager

1 0