Boost C++ Libraries: Ticket #6663: Avoiding input copying

anonymous — Thu, 08 Mar 2012 18:49:24 GMT

Lexical cast has optimizations for almost all basic input types (char*, signed char*, unsigned char*, std::string, std::wstring, char, int, ...)
Are you just requesting an additional overload with (const char*, size_t) parameters?

Thu, 08 Mar 2012 18:51:54 GMT

Yes, as the input isn't (and can't be) null-terminated.

Marshall Clow — Thu, 08 Mar 2012 19:00:05 GMT

This might be a use for string_ref, which I've been itching to get into boost.

See http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3334.html

Antony Polukhin — Thu, 08 Mar 2012 19:04:14 GMT

Replying to marshall:

This might be a use for string_ref, which I've been itching to get into boost.

See http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3334.html

I love the idea[[BR]] Also, I was thinking about providing optimized conversions for iterator_range<SOME_CHAR_TYPE> (described in ticket #6430). I think it would be a good solution for situations, when input chars are not NULL terminated. Such approach will be described in FAQ section of lexical_cast documentation.

Thu, 08 Mar 2012 19:06:20 GMT

Hehe, that can't be a coincedence. :p

http://code.google.com/p/xbt/source/browse/trunk/xbt/misc/xbt/data_ref.h#133

status changed; resolution set

Antony Polukhin — Sat, 24 Mar 2012 19:35:22 GMT

status new → closed
resolution → fixed

(In [77517]) Fixes #6663 (much more optimizations for iterator_range, updated documentation and performance test results)

olafvdspek@… — Sat, 24 Mar 2012 21:59:47 GMT

No (const char*, size_t) overload? :(

In the examples, you might want to use size() instead of length(). size() is used more often.

Antony Polukhin — Sun, 25 Mar 2012 05:45:11 GMT

Updated documentation in r77537
Still thinking about (const CharT*, size_t) overloads. Lexical_cast was initially designed to be a wrapper around stream input and output operators. However (const CharT*, size_t) overloads will add some syntax sugar and reduce compilation time (less metaprogramming can be used).

olafvdspek@… — Sun, 25 Mar 2012 20:51:39 GMT

It'd still use stream input operators, right? To me, that overload is the logical base of optimizations for other overloads, like const char* and std::string.

status changed; resolution deleted

Antony Polukhin — Mon, 26 Mar 2012 18:48:46 GMT

status closed → reopened
resolution fixed

I'll add (const CharT*, size_t) overloads after dealing with #6717. But I don't think that (const CharT*, size_t) overloads will appear in 1.50 release.

Antony Polukhin — Mon, 16 Apr 2012 17:13:14 GMT

(In [78015]) Comment out bad advise in documentation ( refs #6786, refs #6663)

Antony Polukhin — Tue, 17 Apr 2012 16:27:54 GMT

(In [78044]) Update documentation ( more info about stream character type detection + warn about new unicode types support; refs #6786, refs #6663)

Antony Polukhin — Wed, 18 Apr 2012 04:09:52 GMT

(In [78059]) Merge lexical_cast library from trunk:

multiple optimizations and bugfixes for boost::iterator_range (refs #6786, refs #6430, refs #6663)
documentation update
new Unicode characters support updated
much more tests, removed incorrect tests

Antony Polukhin — Tue, 28 Aug 2012 20:31:19 GMT

(In [80291]) Added lexical_cast(const CharType* chars, std::size_t count) function overload (refs #6430 and refs #6663) Fixed GCC warning in numeric_cast_test.cpp

Tue, 28 Aug 2012 21:05:46 GMT

Shouldn't you use data() instead of c_str()? The terminator isn't required.

Antony Polukhin — Mon, 03 Sep 2012 17:21:18 GMT

Replying to Olaf van der Spek <olafvdspek@…>:

Shouldn't you use data() instead of c_str()? The terminator isn't required.

You are right, that would be more appropriate. Just out of curiosity: modern std::basic_string implementations make a difference between data() and c_str()? (Looked through GCC sources, both calls are evaluated to _M_data(); call)

Antony Polukhin — Mon, 03 Sep 2012 17:23:19 GMT

(In [80377]) Replace .c_str() with .data() in documentation (refs #6663)

Mon, 03 Sep 2012 17:35:01 GMT

Replying to apolukhin:

Just out of curiosity: modern std::basic_string implementations make a difference between data() and c_str()? (Looked through GCC sources, both calls are evaluated to _M_data(); call)

Don't know, but I doubt it.

Antony Polukhin — Wed, 05 Sep 2012 18:23:43 GMT

(In [80409]) Merge from trunk: 1) #warning replaced with #error (refs #7228) 2) Pavel Korzh added to thanks list (refs #7157) 3) BOOST_NOEXCEPT modifiers added where possible 4) better support for c++11 Unicode characters 5) fixed compilation with MSVC+STLPort 6) more agressive usage of Traits template parameter 7) Added lexical_cast(const CharType* chars, std::size_t count) function overload (refs #6430 and refs #6663) 8) Fixed GCC warning in numeric_cast_test.cpp 9) Fix compilation of lexical cast with MSVC 2003 (refs #7255)

status, milestone changed; resolution set

Antony Polukhin — Sat, 15 Sep 2012 07:33:23 GMT

status reopened → closed
resolution → fixed
milestone To Be Determined → Boost 1.52.0