Re: [boost] [lexical-cast] version of lexical_cast in 1.46.1 is quite older than in trunk
"SergV"<serge-voropaev@yandex.ru> wrote in message news:loom.20110329T052451-354@post.gmane.org... We discovered lexical_cast from 1.43 and 1.46.1 versions do not work in our program. But version of lexical_cast from trunk work very well. Version information: 1.46.1 - rev. 56161 13.09.2009 trunk - rev.65279 5.09.2010
1) Is there any reason that release does not include last version lexical_cast from trunk? 2) May be there are a lot of such forgotten files in trunk?
There is also some mess with tickets for lexical_cast : some tickets are in bug database for months (and even years).
On Wed, 2011-03-30 at 18:16 +0300, Matthew Chambers wrote:
Does that mean lexical_cast is orphaned? I'd like to see lexical_cast have optimized conversions for string->number and number->string (template specializations using strtol/strtod; or optionally using the spirit-based construe_cast). Being able to pass ios flags to control the format (i.e. boolalpha) would be nice too [...] Which reminds me - lexical_cast error messages are not very informative[...]
Agreed. This should be added as well[...]
-Matt
I can take care about some of this issues, but if lexical_cast is orphaned and not maintained any more it`ll be just wasting time. - Antony
Antony Polukhin wrote:
On Wed, 2011-03-30 at 18:16 +0300, Matthew Chambers wrote:
Does that mean lexical_cast is orphaned? I'd like to see lexical_cast have optimized conversions for string->number and number->string (template specializations using strtol/strtod; or optionally using the spirit-based construe_cast). Being able to pass ios flags to control the format (i.e. boolalpha) would be nice too [...] Which reminds me - lexical_cast error messages are not very informative[...]
Agreed. This should be added as well[...]
I can take care about some of this issues, but if lexical_cast is orphaned and not maintained any more it`ll be just wasting time.
Not true. You and others will benefit from the patches. First, they can be applied manually to local Boost installations, even if they aren't part of a Boost release. Second, others, with commit permission, can apply the patches even without an active maintainer if they are sufficiently comfortable with doing so (and there's enough noise to get their attention). Besides, you could volunteer to be the maintainer! _____ Rob Stewart robert.stewart@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.
Stewart, Robert wrote:
Not true. You and others will benefit from the patches. First, they can be applied manually to local Boost installations, even if they aren't part of a Boost release. Second, others, with commit permission, can apply the patches even without an active maintainer if they are sufficiently comfortable with doing so (and there's enough noise to get their attention). Besides, you could volunteer to be the maintainer!
No objections from me (the current maintaier). I don't have time for this any more. Alex
Alexander Nasonov <alnsn <at> yandex.ru> writes:
No objections from me (the current maintaier). I don't have time for this any more.
Do you have time to do merge release and trunk? Sergey Voropaev
participants (4)
-
Alexander Nasonov -
Antony Polukhin -
Sergey Voropaev -
Stewart, Robert