Using string.at() or string[]

Question

In C++, is it bad to use string[x] to get a char at a specific location? Most people use string.at(x) but is there a reason why string[x] is bad?

The real question is not "whether one is better or worse", but "what's the difference and when to use each". — Aleksei Zabrodskii
– Aleksei Zabrodskii, Commented Oct 8, 2013 at 4:32

Adam · Accepted Answer · 2013-10-08 04:28:28Z

10

As far as I'm aware most people don't use string.at(). If your code is well written and well understood, you should always be working within the bounds of your string so don't need the run-time bounds checking that string.at() provides. Same goes for the other sequence containers with .at().

edited Oct 8, 2013 at 4:28

Adam

17.5k8 gold badges55 silver badges103 bronze badges

answered Oct 8, 2013 at 3:54

goji

7,1813 gold badges45 silver badges62 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

syam Over a year ago

In addition, random access in strings is seldom required, the vast majority of string operations can be performed using sequential access (ie. using iterators instead of indexes). Same goes with other sequence containers.

Pete Becker Over a year ago

+1 for designing code to work correctly rather than adding random hacks to catch mistakes.

Collectives™ on Stack Overflow

Using string.at() or string[]

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related