Boost C++ Libraries: Ticket #471: boost.range and "const char[]".

nobody — Fri, 26 Aug 2005 05:20:57 GMT

Logged In: NO
The size is supposed to be 3 in this example. As described in the C++
standard, C-style strings include a terminating "\0" character. Your string
will have 3 characters, '\0', 'A', and '\0'.

sergey_shandar — Fri, 26 Aug 2005 07:23:17 GMT

Logged In: YES
user_id=957289
I know that a size of this array is 3. boost::size(A) should
return 2 because of
http://www.boost.org/libs/range/doc/boost_range.html#size.
But it returns 0. The problem is boost::size and boost::end
handles A as "const char *" instead of "const char[3]".
I have not checked other functions as rbegin.

Thorsten Ottosen — Fri, 07 Oct 2005 01:05:45 GMT

Logged In: YES
user_id=637229
The support for string arguments is deprecated and will go
away in the next major release. According to the current
implementation, the code behaves just as designed.
br
Thorsten

status changed

sergey_shandar — Tue, 25 Oct 2005 07:41:47 GMT

status assigned → closed

Logged In: YES
user_id=957289
>According to the current
implementation, the code behaves just as designed.
No, it doesn't. Accordint to the documentation
http://www.boost.org/libs/range/doc/boost_range.html#size it
MUST return 2 but it returns 0. It's a serious bug. Change
either documentation or code.

Thorsten Ottosen — Mon, 23 Oct 2006 13:42:25 GMT

Logged In: YES
user_id=637229
arrays (and so string literals) have their size deduced at
compile-time. Embedding a null will not change that.
What is the use of the literal above anyway?
-Thorsten

sergey_shandar — Mon, 23 Oct 2006 14:07:53 GMT

Logged In: YES
user_id=957289
>arrays (and so string literals) have their size deduced at
compile-time. Embedding a null will not change that.
Yeah, it would be good if it beahaves like this. However,
according to example, the size depends on a position of a
null so boost::size(A) == 0 (Boost 1.33). Sure I expected
compile time - 2.
>What is the use of the literal above anyway?
It's just a minimal example that shows a bug in Boost.Range
1.33, I don't know much about 1.34. I prefer compile time
computation where it's possible. Currently, I use my own
range library (http://cbear.berlios.de/range), it doesn't
accept char* and wchar_t* as a range. Only T(&)[N] types
are accepteble.

anonymous — Tue, 05 Jun 2007 02:30:17 GMT

The same bug in 1.34

status, component, description changed; severity set

Marshall Clow — Tue, 21 Aug 2007 21:06:49 GMT

status assigned → new
component None → range
description modified (diff)
severity → Problem

anonymous — Thu, 06 Sep 2007 06:39:45 GMT

1.34.1 has the same bug.

status, resolution changed

Thorsten Ottosen — Tue, 23 Oct 2007 18:45:20 GMT

status new → closed
resolution Rejected → wontfix

For 1.35 I have added this test:

const char A[] = "\0A"; BOOST_CHECK_EQUAL( boost::size(A), 3u );

This is the bahavior of 1.35.