November 2013 - Boost - lists.preview.boost.org

New Version (0.4) of Boost.Application (Aspect Based) available to comments (RFC).
by Renato Forti 09 Nov '13

09 Nov '13

Hi, I will answer on list too. >> I would like to know if your application class is related only to console applications or is it a generic class that could be implemented also as a gui::application? It is generic. But now we don't provide any specific support to GUI, you can for sample use it with QT, to do this you need use "common mode". >> I'm trying to write a cross platform header only gui library, so I wonder if I should use it (hoping it's a header only library too) or have my own different gui::application class. http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/boost_applica tion/f_a_q_.html#boost_application.f_a_q_.can_i_build_another_application_mo de__what_is_needed_ Well, you can build a application mode that will use your GUI lib, e.g. application::gui use application::common as model. But we have some problem here! 1. Boost.Application is not a boost library yet! (have no support od boost.org) , and it is in working progress status. Things can change! 2. Boost.Application is header only, but have some dependencies that are not header only. http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/boost_applica tion/dependencies.html PS. If you think that this library is interesting to boost, please post on boost.devel, that you have interest on it. http://news.gmane.org/gmane.comp.lib.boost.devel Hope this helps in your decision. If you have any other questions, let me know! -- Renato Forti

1 0

New Version (0.4) of Boost.Application (Aspect Based) available to comments (RFC).
by Renato Forti 09 Nov '13

09 Nov '13

Hi Stas, Thanks for your comments! >> I think it worth noting in documentation that SIGUSR1 is reserved for internal purposes. I will do! >> What do you think about self pipe built-in functionality? It is a widely used trick. I think it can be implemented as an aspect in a quite straightforward way. Can you give more details about what you're proposing here? Elegant signal handler is my main problem in this lib! I want ideas to get it correctly designed! Thanks for documentation appointments, I will fix all! And I forgot to put the main question on message: "Is there any interest in a library like this?" What you think? Thanks a lot!

3 4

[string_ref] string literal constructor
by Michael Marcin 08 Nov '13

08 Nov '13

I noticed string_ref doesn't have a constructor for a string literal. Wouldn't this save a call to strlen for a common case? Ex. template< std::size_t N > basic_string_ref( const charT( &str )[N] ) : basic_string_ref( str, N-1 ) { static_assert(N >= 1, "not a string literal"); } string_ref test( "test" ); I see that adding this directly doesn't work as the compiler is always choosing to decay and pick the const char* overload. Is there no way to make this work?

10 15

New Version (0.4) of Boost.Application (Aspect Based) available to comments (RFC).
by Renato Forti 07 Nov '13

07 Nov '13

Hi All, I have a new "Prototype" version (Version 0.4) of Boost.Application ready to use. This version use a concept of "aspects" suggested by 'Vicente J. Botet Escriba'. Thus the library is much more flexible than version 0.3 (old-version), now the components are independents (loosely coupled). The documentation (work in progress status) is available on : <http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/index.html> http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/index.html The lib can be downloaded on : <https://github.com/retf/Boost.Application> https://github.com/retf/Boost.Application Please send your feedback! -- Older Version (0.3): If you want to make a comparison with the previous version (0.3), check: <http://www.dokfile.com/appbeta3/docs/libs/application/doc/html/index.html> http://www.dokfile.com/appbeta3/docs/libs/application/doc/html/index.html Thanks

2 1

[1.55.0] Release candidate 2 available
by Marshall Clow 07 Nov '13

07 Nov '13

RC2 files for 1.55.0 are available at http://boost.cowic.de/rc/ As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. This helps ensure the candidates build OK before we push them out to SourceForge. The files (and associated md5s) are: 93780777cfbf999a600f62883bd54b17 *boost_1_55_0_rc2.tar.gz d6eef4b4cacb2183f2bf265a5a03a354 *boost_1_55_0_rc2.tar.bz2 8aca361a4713a1f491b0a5e33fee0f1f *boost_1_55_0_rc2.zip 4e5bbc15fc8c80df8be428f8a5b5a823 *boost_1_55_0_rc2.7z Thanks! -- The release managers === Changes to release since rc1 === ---- Author: bemandawes Date: 2013-10-28 13:16:50 EDT (Mon, 28 Oct 2013) New Revision: 86503 URL: http://svn.boost.org/trac/boost/changeset/86503 Log: Merge 86426 from trunk. This should fix msvc test failures. ---- Author: bemandawes Date: 2013-10-29 09:15:03 EDT (Tue, 29 Oct 2013) New Revision: 86514 URL: http://svn.boost.org/trac/boost/changeset/86514 Log: Merge 84443 from trunk, to fix mpl assert failures for msvc in many libraries. ---- Author: eric_niebler Date: 2013-10-29 12:53:08 EDT (Tue, 29 Oct 2013) New Revision: 86516 URL: http://svn.boost.org/trac/boost/changeset/86516 Log: merge [86460] from trunk, fix bootstrap on mingw --- Author: jhunold Date: 2013-10-29 13:19:33 EDT (Tue, 29 Oct 2013) New Revision: 86519 URL: http://svn.boost.org/trac/boost/changeset/86519 Log: Merge 84402 from ^/trunk ------------------------------------------------------------------------ r84402 | jhunold | 2013-05-21 14:23:20 +0200 (Di, 21 Mai 2013) | 4 lines Fix: cache file loading and saving must use native paths Fixes caching at least on Windows platform ------------------------------------------------------------------------ --- Author: johnmaddock Date: 2013-11-01 05:32:55 EDT (Fri, 01 Nov 2013) New Revision: 86532 URL: http://svn.boost.org/trac/boost/changeset/86532 Log: Merge fix for dependency tracking. --- Author: danieljames Date: 2013-11-03 14:20:09 EST (Sun, 03 Nov 2013) New Revision: 86551 URL: http://svn.boost.org/trac/boost/changeset/86551 Log: Merge Visual C++ 12 fix for Unordered. --- Author: viboes Date: 2013-11-03 15:43:42 EST (Sun, 03 Nov 2013) New Revision: 86552 URL: http://svn.boost.org/trac/boost/changeset/86552 Log: Thread: merge [86540] to fix #9319.

11 16

Re: [boost] [1.55.0] Release candidate 2 available
by Peter Dimov 06 Nov '13

06 Nov '13

Robert Ramey wrote: > lol - I'm already dealing with the fallout from a previous "trivial one > line fix". I actually do understand, because most trivial one-line fixes aren't. This one (adding the missing #include <algorithm>) really is, though. (At least according to my experience.)

1 0

Re: [boost] [1.55.0] Release candidate 2 available
by Eric Niebler 06 Nov '13

06 Nov '13

On 11/5/2013 1:46 AM, LeMay.Steve wrote: > VS2013 needs archive's transform_width.hpp to #include <algorithm> so > that std::min will be properly defined. Looks like it. Can you file the bug please? -- Eric Niebler Boost.org http://www.boost.org

11 17

[math] Contribution and TODO-list implementation.
by Bikineev 06 Nov '13

06 Nov '13

Hello. I'm russian student. My department is Applied Math. I need to make my magister work and I would like to relate it with Boost.Math development. I think this work could be something like implementation of tasks mentioned in TODO-list. New feature development may take a long time. In the best case, I would be glad to take job and reviewer for it. If anyone has an idea - I'm ready to take serious and big job for 1,5 years. Thanks.

5 11

Boost API System or Library Calls ..
by Rahul Mathur 06 Nov '13

06 Nov '13

Out of curiosity, wish to know if BOOST ASIO calls like - boost::asio::read() boost::asio::transfer_all() boost::asio::write() BOOST LEXICAL calls like - boost::lexical_cast<std::string>() BOOST POSIX TIME calls like - boost::posix_time::microsec_clock::universal_time() boost::posix_time::microsec_clock::ptime() are LIBRARY or SYSTEM calls. How to know which calls of BOOST are SYSTEM and LIBRARY calls? Thanks.

3 3

Re: [boost] [modularization] Dependency to Boost.Exceptionunavoidable?
by Ahmed Charles 05 Nov '13

05 Nov '13

What about combining throw_exception.hpp and exception.hpp and move that header to config, since it won't depend on anything else and only really does configuration anyways? Note, if you don't like config as a choice, the new version of detail which only depends on config sounds nice as well. ________________________________ From: Emil Dotchevski Sent: 11/3/2013 12:29 PM To: boost(a)lists.boost.org Subject: Re: [boost] [modularization] Dependency to Boost.Exceptionunavoidable? On Sat, Nov 2, 2013 at 5:19 PM, Niall Douglas <s_sourceforge(a)nedprod.com> wrote: > On 1 Nov 2013 at 16:01, Emil Dotchevski wrote: > >> 1. If BOOST_NO_EXCEPTIONS is defined, libraries should not throw. One >> option to implement that behavior is to pass exception objects (of the >> usual documented library-defined types) to boost::throw_exception. > > I wonder how useful supporting exceptions disabled is in recent years? I agree that many Boost libraries are impractical with exception handling disabled, but there is no harm done in supporting BOOST_NO_EXCEPTIONS via boost::throw_exception, since its specification does not allow it to return. -- Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

3 3