CARVIEW

MOTORHOMES

Select Language

HTTP/2 200 date: Mon, 28 Jul 2025 18:26:24 GMT content-type: text/html; charset=utf-8 cf-ray: 96666cb1dd83c469-BLR cf-cache-status: DYNAMIC cache-control: private set-cookie: prov=ea380065-d84a-480c-99d8-a4b27710a832; expires=Tue, 28 Jul 2026 18:26:24 GMT; domain=.stackexchange.com; path=/; secure; httponly strict-transport-security: max-age=31536000; includeSubDomains vary: Accept-Encoding content-security-policy: upgrade-insecure-requests; frame-ancestors 'self' https://stackexchange.com x-clacks-overhead: GNU Terry Pratchett x-frame-options: SAMEORIGIN x-request-guid: 52167da3-8beb-49d6-89ff-51a09a5ea190 x-worker-origin-response-time: 769000000 x-dns-prefetch-control: off set-cookie: prov=ea380065-d84a-480c-99d8-a4b27710a832; Path=/; HttpOnly; Domain=stackexchange.com set-cookie: __cf_bm=cy.04miGJXlNekQDsKJBL4p4O0lpqXqsk46Mex055pQ-1753727184-1.0.1.1-1vbOSLOFfDtb2aL5Ybb3pAKPxs4Pmg4i2_7HNEqLn2gg_NIK4SS7INYsesleCX0bNF36nHle3ofVFT0KaKwnSP4Si4kwUn3X2BjzaQCAngY; path=/; expires=Mon, 28-Jul-25 18:56:24 GMT; domain=.stackexchange.com; HttpOnly; Secure; SameSite=None set-cookie: _cfuvid=cVee1sdaOyuBPVZAGoZ.B8ey6Mx8_rY4vW3J8d074pU-1753727184446-0.0.1.1-604800000; path=/; domain=.stackexchange.com; HttpOnly; Secure; SameSite=None server: cloudflare content-encoding: gzip Revisions to Review of three constructors for a String class - Code Review Stack Exchange

1. Home
2. Questions
3. Unanswered
4. AI Assist Labs
5. Tags
7. Chat
8. Users
10. Companies
Teams

Ask questions, find answers and collaborate at work with Stack Overflow for Teams.
Try Teams for free Explore Teams
Teams
Ask questions, find answers and collaborate at work with Stack Overflow for Teams. Explore Teams

Return to Answer

replaced https://stackoverflow.com/ with https://stackoverflow.com/

Source Link

edited May 23, 2017 at 12:41

Community Bot

When dealing with length, prefer std::size_t. This is an unsigned integer type that is also the return type of the sizeof operator. It is not good to use int because you cannot guarantee that any length will fit. Your code will break if the user constructs an object that is too large. There's also this issue this issue. Accordingly, your loop counter type throughout the class should be std::size_t.

CORRECTION: @LokiAstari has pointed out that this is now wrong, according to Bjarne Stroustrup (the creator of C++) and other top C++ experts.

The main consensuses here are that:

mismatching signed/unsigned is a source of bugs
prefer signed unless the extra bit is needed for larger values
the STL was wrong about this all along

More information can be found here:

When dealing with length, prefer std::size_t. This is an unsigned integer type that is also the return type of the sizeof operator. It is not good to use int because you cannot guarantee that any length will fit. Your code will break if the user constructs an object that is too large. There's also this issue. Accordingly, your loop counter type throughout the class should be std::size_t.

CORRECTION: @LokiAstari has pointed out that this is now wrong, according to Bjarne Stroustrup (the creator of C++) and other top C++ experts.

The main consensuses here are that:

mismatching signed/unsigned is a source of bugs
prefer signed unless the extra bit is needed for larger values
the STL was wrong about this all along

More information can be found here:

When dealing with length, prefer std::size_t. This is an unsigned integer type that is also the return type of the sizeof operator. It is not good to use int because you cannot guarantee that any length will fit. Your code will break if the user constructs an object that is too large. There's also this issue. Accordingly, your loop counter type throughout the class should be std::size_t.

CORRECTION: @LokiAstari has pointed out that this is now wrong, according to Bjarne Stroustrup (the creator of C++) and other top C++ experts.

The main consensuses here are that:

mismatching signed/unsigned is a source of bugs
prefer signed unless the extra bit is needed for larger values
the STL was wrong about this all along

More information can be found here:

added 603 characters in body; Post Made Community Wiki

Source Link

edited Nov 25, 2013 at 0:20

Jamal

35.2k
13
134
238

When dealing with length, prefer std::size_t. This is an unsigned integer typeWhen dealing with length, prefer std::size_t. This is an unsigned integer type that is also the return type of the sizeof operator. It is not good to use int because you cannot guarantee that any length will fit. Your code will break if the user constructs an object that is too large. There's also this issue. Accordingly, your loop counter type throughout the class should be std::size_t.

CORRECTION: @LokiAstari has pointed out that is also the return type of the sizeof operator. It is not goodthis is now wrong, according to useBjarne Stroustrup int because you cannot guarantee that any length will fit(the creator of C++) and other top C++ experts. Your code will break if the user constructs an object

The main consensuses here are that is too large. There's also this issue. Accordingly, your loop counter type throughout the class should:

mismatching signed/unsigned is a source of bugs

prefer signed unless the extra bit is needed for larger values

the STL was wrong about this all along

More information can be std::size_t.found here:

Going Native

Interactive Panel: Ask Us Anything

When dealing with length, prefer std::size_t. This is an unsigned integer type that is also the return type of the sizeof operator. It is not good to use int because you cannot guarantee that any length will fit. Your code will break if the user constructs an object that is too large. There's also this issue. Accordingly, your loop counter type throughout the class should be std::size_t.

CORRECTION: @LokiAstari has pointed out that this is now wrong, according to Bjarne Stroustrup (the creator of C++) and other top C++ experts.

The main consensuses here are that:

mismatching signed/unsigned is a source of bugs

prefer signed unless the extra bit is needed for larger values

the STL was wrong about this all along

More information can be found here:

Going Native

Interactive Panel: Ask Us Anything

Source Link

answered Oct 31, 2013 at 2:53

Jamal

35.2k
13
134
238

When dealing with length, prefer std::size_t. This is an unsigned integer type that is also the return type of the sizeof operator. It is not good to use int because you cannot guarantee that any length will fit. Your code will break if the user constructs an object that is too large. There's also this issue. Accordingly, your loop counter type throughout the class should be std::size_t.

Original Source | Taken Source