- Boost - lists.boost.org

Re: [boost] [filesystem] Linker error against std::codecvt in VS2012 RC
by Stewart, Robert 01 Jun '12

01 Jun '12

Peter Dimov wrote: > Lars Viklund wrote: > > > [1] 1>libboost_filesystem-vc110-mt-gd-1_50.lib(path.obj) : > > error LNK2001: unresolved external symbol "protected: virtual > > int __thiscall std::codecvt<wchar_t,char,int>::do_length(int > > const &,char const *,char const *,unsigned int)const " > > (?do_length@?$codecvt@_WDH@std@@MBEHABHPBD1I@Z) > > Well, you could start by preparing a simple test program that > calls std::codecvt in the same way path.obj does, to eliminate > Boost as a factor. If do_length is indeed not present in the > dynamic runtime, this would probably be a showstopper bug > against the RC, so it will get noticed. :-) If that's not the problem, verify that you built Boost.Filesystem using the same CRT. _____ Rob Stewart robert.stewart(a)sig.com Software Engineer using std::disclaimer; Dev Tools & Components Susquehanna International Group, LLP http://www.sig.com ________________________________ IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.

2 1

Re: [boost] [Boost-users] [review] Multiprecision review scheduled for June 8th - 17th, 2012
by Jeffrey Lee Hellrung, Jr. 31 May '12

31 May '12

Just to preempt this, I think it will be more appropriate for any review discussions to take place on the developers' list (boost(a)lists.boost.org) On Wed, May 30, 2012 at 2:38 PM, Vicente J. Botet Escriba < vicente.botet(a)wanadoo.fr> wrote: > Le 29/05/12 23:08, Jeffrey Lee Hellrung, Jr. a écrit : > > Hi all, > > > > The review of the proposed Boost.Multiprecision library authored by John > Maddock and Christopher Kormanyos has been scheduled for > > > > June 8th - June 17th, 2012 > > > > and will be managed by myself. > > > > I hope everyone interested can reserve some time to read through the > documentation, try the code out, and post a formal review, either during > the formal review window or before. > > > Hi, > > glad to see that the library will be reviewed soon. > > I have spent some hours reading the documentation. Here are some comments > and a lot of questions. > > * As all the classes are at the multi-precision namespace, why name the > main class mp_number and not just number? > > typedef mp::number<mp::mpfr_float_**backend<300> > my_float; > > * I think that the fact that operands of different backends can not be > mixed on the same operation limits some interesting operations: > > I would expect the result of unary operator-() always signed? Is this > operation defined for signed backends? > I would expect the result of binary operator-() always signed? Is this > operation defined for signed backends? what is the behavior of > mp_uint128_t(0) - mp_uint128_t(1)? > > It would be great if the tutorial could show that it is possible however > to add a mp_uint128_t and a mp_int256_t, or isn't it possible? > I guess this is possible, but a conversion is needed before adding the > operands. I don't know if this behavior is not hiding some possible > optimizations. > > I think it should be possible to mix backends without too much complexity > and that the library could provide the mechanism so that the backend > developer could tell to the library about how to perform the operation and > what should be the result. > > * Anyway, if the library authors don't want to open to this feature, the > limitation should be stated more clearly, e.g in the reference documentation > "The arguments to these functions must contain at least one of the > following: > > An mp_number. > An expression template type derived from mp_number. > " > there is nothing that let think mixing backend is not provided. > > * What about replacing the second bool template parameter by an enum class > expression_template {disabled, enabled}; which will be more explicit. That > is > > typedef mp::mp_number<mp::mpfr_float_**backend<300>, false> my_float; > > versus > > typedef mp::mp_number<mp::mpfr_float_**backend<300>, > mp::expression_template::**disabled> my_float; > > * As I posted in this ML already I think that allocators and precision are > orthogonal concepts and the library should allow to associate one for fixed > precision. What about adding a 3rd parameter to state if it is fixed or > arbitrary precision? > > * Why cpp_dec_float doesn't have a template parameter to give the integral > digits? or as the C++ standard proposal from Lawrence Crow ( > http://www.open-std.org/jtc1/**sc22/wg21/docs/papers/2012/**n3352.html<http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3352.html>), > take the range and resolution as template parameters? > > * What about adding Throws specification on the mp_number and backend > requirements operations documentation? > > * Can the user define a backend for fixed int types that needs to manage > with overflow? > > * Why bit_set is a free function? > > * I don't see nothing about overflow for cpp_dec_float backend operations. > I guess it is up to the user to avoid overflow as for integers. what would > be the result on overflow? Could this be added to the documentation? > > * can we convert from a cpp_dec_float_100 to a cpp_dec_float_50? if yes, > which rounding policy is applied? Do you plan to let the user configure the > rounding policy? > BTW, I see in the reference "Type mp_number is default constructible, and > both copy constructible and assignable from: ... Any type that the Backend > is constructible or assignable from. " > I would expect to have this information in some way on the tutorial. I > will appreciate also if section "Constructing and Interconverting Between > Number Types" says something about convert_to<T> member function. > > If not, what about a mp_number_cast function taking as parameter a > rounding policy? > > * Does the cpp_dec_float back end satisfies any of the Optional > Requirements? The same question for the other backends? > > * Is there a difference between implicit and explicit construction? > * On c++11 compilers providing explicit conversion, couldn't the > convert_to function be replaced by a explicit conversion operator? > * Are implicit conversion possible? > > * Do you plan to add constexpr and noexcept to the interface? After > thinking a little bit I'm wondering if this is this possible when using 3pp > libraries backends that don't provide them? > > * Why do you allow the argument of left and right shift operations to be > signed and throw an exception when negative? Why don't just forbid it for > signed types? > > * Why the "Non-member standard library function support" can be used only > with floating-point Backend types? Why not with fixed-point types? > > * What is the type of boost::multiprecision::number_**category<B>::type > for all the provided backends? Could the specialization for > boost::multiprecision::number_**category<B>::type be added in the > documentation of each backend? and why not add also B::signed_types, > B::unsigned_types, B::float_types, B::exponent_type? > > * Why have you chosen the following requirements for the backend? > - negate instead of operator-() > - eval_op instead of operator op=() > - eval_convert_to instead of explicit operator T() > - eval_floor instead of floor > > Optimization? Is this optimization valid for short types (e.g. up to 4/8 > bytes)? > > * As the developer needs to define a class with some constraints to be a > model of backend, which are the advantages of requiring free functions > instead of member functions? > * Couldn't these be optional if the backend defines the usual operations? > * Or could the library provide a trivial backend adaptor that requires the > backend just to provide the usual operations instead of the eval_xxx? > * How the performances of mp_number<this_trivial_**adaptor<float>, false> > will compare with float? > > * And last, I don't see anything related to rvalue references and move > semantics. Have you analyzed if its use could improve the performances of > the library? > > Good luck for the review. A really good work. > Vicente > > > ______________________________**_________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/**mailman/listinfo.cgi/boost-**users<http://lists.boost.org/mailman/listinfo.cgi/boost-users> >

3 2

[nowide] Easy Unicode For Windows: Request For Comments/Preliminary Review
by Artyom Beilis 31 May '12

31 May '12

Hello all Booster, I comments on a library that I want to submit for a formal review. The library provides an implementation of standard C and C++ library functions such that their inputs are UTF-8 aware on Windows without requiring using Wide API to make program work on Windows. Library: Boost.Nowide Download: http://cppcms.com/files/nowide/nowide.zip Documents: http://cppcms.com/files/nowide/html/ Features: http://cppcms.com/files/nowide/html/index.html#main_the_solution Tested On: OS: Windows 7 32/64 bit, Linux Compilers: GCC-4.6, MSVC-10 Artyom Beilis -------------- CppCMS - C++ Web Framework: http://cppcms.com/ CppDB - C++ SQL Connectivity: http://cppcms.com/sql/cppdb/

7 17

Is there interest in typeid(TYPE).name() like function that does not require RTTI
by Antony Polukhin 30 May '12

30 May '12

Hi, Would be there some interest in function for getting class name without RTTI? Such function can be implemented like that: template <class TemplateNameT> std::string template_type(const TemplateNameT& v) { #ifdef _MSC_VER const char* const template_name_begin = strstr(BOOST_CURRENT_FUNCTION, "(const ") + sizeof("(const ") - 1; BOOST_ASSERT(template_name_begin); const char* const template_name_end = template_name_begin + strlen(template_name_begin) - sizeof("&)"); #else // Code for other platforms #endif return std::string(template_name_begin, template_name_end); } If there is some interest, I'll update code to work on other platforms, and change method signature from template_type(instance) to template_type<InstanceTypeT>::name() Usage example: // Function can be compiled with RTTI disabled. template <class T> void foo(const T& val) { std::cerr << template_type<T>::name(); // instead of typeid(T).name(); } -- Best regards, Antony Polukhin

4 7

[msm] orthogonal region and event consume
by Takatoshi Kondo 30 May '12

30 May '12

Hello Christophe, I'm using Boost.MSM version 1.49.0. I bumped on a suspicious behavior. See the attached diagram and code. When Event1 occurs in State1, Action1 is invoked. I think the event isn't consumed correctly. If the transition from State1 to State2 connect State2 directly instead of Entry1, the event seems to be consumed. What do you think? Thanks, Takatoshi

4 9

Memory upgrade of wowbagger
by DongInn Kim 30 May '12

30 May '12

Dear all, My name is DongInn Kim, systems administrator of the current boost server machine, wowbagger. I am sorry for this short notice but we would like to upgrade wowbagger's memory at 2:00pm (E.T.) May 30, 2012. We need to reboot wowbagger and It should not take more than 10 mins to upgrade RAMs. During the memory upgrade, the following services would not be available. - mailing list - mail archives - trac - subversion - official websites Please let me if you have any issues or questions about the outage. Regards, -- - DongInn --------------------------- CREST System administrator dikim(a)cs.indiana.edu Indiana University Bloomington, IN

1 1

[1.50.0] Beta closing; planning to build Beta RC tomorrow
by Beman Dawes 30 May '12

30 May '12

Per the schedule, building a release candidate for the beta will begin tomorrow. There are still a few hours left for merging emergency bug fixes that are stable in trunk, with a release manager's permission. But that's being charitable. We need to let tests cycle overnight and move forward. This is a beta, after all, and not the final release. branches/release will reopen for bug fixes as soon as the beta ships. See the calendar at http://www.boost.org/community/index.html for the release schedule. --Beman

1 0

Status of Boost.Atomic?
by Sean Chittenden 30 May '12

30 May '12

Does anyone know what the status of Boost.Atomic is? I remember hearing that Boost.Atomic was to be committed by the end of March, but now that we're backed up against the release, it doesn't look like Boost.Atomic is going to make it in to 1.50.0. Is there any chance that someone can push Boost.Atomic along and commit it to trunk so that it can finally get some exposure and possibly make it in to a release? -sc PS CLang 3.1 was released recently with with support for atomics, but the current version of XCode ships a dated version of CLang 3.1 with atomics disabled. This compatibility shim is going to be very useful during the C++11 transition. >>>> Where can I find the latest version of boost.lockfree ? There's nothing >>>> in >>>> the sandbox or the vault (it seems). The latest commit on Tim's public >>>> git >>>> repo was done more than 6 month ago. >>>> >>>> Now that atomic has been accepted, are there any roadblocks to have >>>> boost.lockfree released ? >>> >>> boost.atomic has been accepted, but it hasn't been merged into trunk, yet >>> ... helge, do you have any timeline? >> >> I will package it up before the end of march, this should suffice? > > great! -- Sean Chittenden sean(a)chittenden.org

2 1

Release notes for 1.50
by Daniel James 30 May '12

30 May '12

Hello everyone, It's time to fill in the release notes, they're at: https://svn.boost.org/svn/boost/website/public_html/live/feed/history/boost… Note that from now on, that this is on the live site, not the beta site. If you don't know quickbook syntax, don't worry, I'll clean it up before regenerating the page. You can see the html output at: http://www.boost.org/users/history/version_1_50_0.html It isn't automatically updated, so you'll only see your changes when I update it. But if that's too much for you, you can email me and I'll sort it out. It's probably better for you if do it yourself, as there's always the chance that an email will slip through the cracks, and it will be easier for you to fix typos and link errors later on. Also, please don't link to changesets in the history, if you don't have something to link to, just create a ticket, accept it and close it with a message like: "Fixed in trunk in [1234]. fixed in release in [5678]". It's also a good idea to add a more detailed change log to your library's documentation and link to that. There are a few outstanding things to do, which I should sort out before posting this, but this is at shorter notice than normal. I'll deal with them in the next day or two, so please have a little patience. thanks, Daniel

7 10

Status of GIT and BOOST
by Marshall Clow 29 May '12

29 May '12

[ reposted in its own thread so that it is less easily missed ] Synopsis: ========= The Boost Steering Committee has agreed IN PRINCIPLE to move ahead with the migration to Git and to a modular repository structure. What? ===== Development of Boost will move from a monolithic subversion repository to the much-discussed Git repository structure consisting of one super-module that points (via submodules) to other repositories, each containing an individual Boost library. The Git repositories will be hosted on github. Although Boost will move to a distributed development model, it will still be tested and released as a unified whole. There will be scripts to reassemble the monolithic Boost from its constituents. The development work flow need not change for contributors. They have the option to check out boost super-module and all the submodules, execute the script to make a monolithic whole, and develop and test as usual. It is currently an open question what to do about issue tracking once we move to modularized repos. Both Github and Redmine have been suggested as possible solutions that would give users a unified way to search for bugs across all of boost. The migration will NOT take place before this issue is settled. Why? ==== Boost is big and getting bigger. We've been experiencing scalability problems with our tools and with our release and testing procedures for a while now. The problem is bigger than "subversion commands are slow". Moving a large, diverse library collection forward in lock-step slows down progress. Our solutions to the scalability problems have themselves caused problems. We don't branch from trunk for our releases. Changes languish on trunk because people forget to merge them. Trunk is a wild west where test results for any one library are often broken due to requirements shifting from under it, causing confusion about whether a change can be safely merged to release. And the converse is also true: just because tests are green on trunk is no assurance that a change won't cause problems on release. The solution is to free each library to evolve independently within its own repository. Boost is a collection of the last stable releases of each of its constituent libraries. Library maintainers develop and test against this latest stable library collection and issue rolling releases on their own timetable. Release managers pick which versions of each library to include and have the option to temporarily fork a library to correct integration issues to get a release out, issuing pull requests to get the fixes upstream. The result is a more dynamic, loosly-coupled ecosystem where both the individual libraries and Boost as a whole can move forward more quickly. How? ==== The modular git repositories have already been created along with a script to populate them automatically. At some point, the old svn repo will be locked permanently and the modular git repos will be re-populated from svn. John Wiegley has worked on a script to do the conversion with perfect fidelity. A separate git repo with all of Boost's history will be created such that it can be grafted on to each submodule if desired. That way, each submodule can share history with all the others (a significant space win). The test and release scripts and the website will be updated to account for the new development model. From that point forward, all development will take place in the git repos. The old Trac will eventually be locked and archived. Whatever issue tracking solution we come up with, tickets must be migrated. The plan is still coming together here. Bear with us. When? ===== The approval is IN PRINCIPLE and not IN FACT at this point because the necessary pieces are not yet all in place. In particular, issues such as trac integration and testing are not yet settled. Also, we want a script in hand that verifies that no changesets are lost or munged in the svn->git migration. Once the steering committee is satisfied that all the pieces are in place, we'll give a final go-ahead, the dates will be announced, and the transition will take place. An ETA is hard to predict at this point, but we are aiming for making the switch in the next few months. Possibly after 1.50 or 1.51. Comments: ========= The Boost Steering Committee understands that there is general but not universal support in the Boost community for this migration. The committee came this to decision after long analysis of the ongoing problems facing Boost, and of the merits of the proposed migration. It is the role of the Steering Committee to make difficult decisions like this, even when the wider community is unable to reach universal consensus. We will do everything to make this transition as painless as possible, and to give those not comfortable with git the support they need. We all appreciate your understanding. THANKS: ======= Thanks are due to the many people who have worked over the past few years to make this transition happen, including: Dave Abrahams Daniel Pfeifer John Wiegley Beman Dawes Eric Niebler Troy Straszheim Thanks, guys! Here's to making Boost better, faster and stronger. --Your friendly neighborhood steering committee Beman Dawes Dave Abrahams Hartmut Kaiser Jeff Garland Jon Kalb Marshall Clow Robert Stewart Steven Wantanabe -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki

1 0