As I have learned, one can write the following code:
char *a = new char[50];
for (int i = 0; i < 50; ++i) {
i[a] = '5';
}
It compiles. It works. It does exactly the same as
char *a = new char[50];
for (int i = 0; i < 50; ++i) {
a[i] = '5';
}
Is it just because:
a[b]
is implemented as a macro*(a + b)
by default and the fact that both code samples are valid is just an accident/compiler specific- it's standardized somewhere and the outcome of such algorithms should be the same on every platform
It is reasonable to assume that addition should be commutative, but if we implement operator[]
in that way, we have made something else commutative, what might not be what we wanted.
The interesting fact is that there is no pointer[pointer]
operator, so operator[]
is not a macro.
I know it's bad. I know it's confusing the people who read the code. But I want to know if it's just an accident and it will not work in a distant land where unicorns have seven legs and horns are on their left cheek.
Answer
C++ standard, § 8.3.4, note 7 (page 185) (emphasis mine).
Except where it has been declared for a class (13.5.5), the subscript operator
[]
is interpreted in such a way thatE1[E2]
is identical to*((E1)+(E2))
. Because of the conversion rules that apply to+
, ifE1
is an array andE2
an integer, thenE1[E2]
refers to theE2
-th member ofE1
. Therefore, despite its asymmetric appearance, subscripting is a commutative operation.
No comments:
Post a Comment