Return to Answer

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

edited May 23, 2017 at 12:40

edited May 23, 2017 at 12:40

Just some quick things:

unsigned int width doesn't need to be const since it's passed-by-value. But that's not really significant as the compiler will optimize away the const if needed.
Prefer size_t size_t for types representing sizes. It's also useful for loop counters as you'll be able to loop through any size of data supported by your computer. However, you'll receive type-matching warnings if your counter and size types are not both signed or unsigned. In this case, using int (which is a signed type) will cause such warnings if the size type is unsigned.

Just some quick things:

unsigned int width doesn't need to be const since it's passed-by-value. But that's not really significant as the compiler will optimize away the const if needed.
Prefer size_t for types representing sizes. It's also useful for loop counters as you'll be able to loop through any size of data supported by your computer. However, you'll receive type-matching warnings if your counter and size types are not both signed or unsigned. In this case, using int (which is a signed type) will cause such warnings if the size type is unsigned.

Just some quick things:

unsigned int width doesn't need to be const since it's passed-by-value. But that's not really significant as the compiler will optimize away the const if needed.
Prefer size_t for types representing sizes. It's also useful for loop counters as you'll be able to loop through any size of data supported by your computer. However, you'll receive type-matching warnings if your counter and size types are not both signed or unsigned. In this case, using int (which is a signed type) will cause such warnings if the size type is unsigned.

Post Undeleted by Jamal

occurred Nov 26, 2013 at 1:08

added 125 characters in body

edited Nov 26, 2013 at 1:08

edited Nov 26, 2013 at 1:08

Just some quick things:

unsigned int width doesn't need to be a const parameter since it's a builtpassed-in type, but it'sby-value. But that's not really a big dealsignificant as such uses ofthe compiler will optimize away the const don't hurt. Just wanted to make a note about thatif needed.
Prefer size_tsize_t for types representing sizes. This can replace every int It's also useful for such variables, especially the loop countercounters as you'll be able to loop through any size of data supported by your computer. You'll get However, you'll receive type-matching warnings if your counter type differs from theand size type in the looptypes are not both signed or unsigned. In most casesthis case, using int (which is a signed type) will cause such warnings since it also uses negative numbersif the size type is unsigned.

Just some quick things:

unsigned int width doesn't need to be a const parameter since it's a built-in type, but it's not really a big deal as such uses of const don't hurt. Just wanted to make a note about that.
Prefer size_t for types representing sizes. This can replace every int for such variables, especially the loop counter. You'll get type-matching warnings if your counter type differs from the size type in the loop. In most cases, using int will cause such warnings since it also uses negative numbers.

Just some quick things:

unsigned int width doesn't need to be const since it's passed-by-value. But that's not really significant as the compiler will optimize away the const if needed.
Prefer size_t for types representing sizes. It's also useful for loop counters as you'll be able to loop through any size of data supported by your computer. However, you'll receive type-matching warnings if your counter and size types are not both signed or unsigned. In this case, using int (which is a signed type) will cause such warnings if the size type is unsigned.

Post Deleted by Jamal

occurred Nov 24, 2013 at 1:48

added 4 characters in body

edited Aug 11, 2013 at 19:54

edited Aug 11, 2013 at 19:54

Just some quick things:

const unsigned int width doesn't needneed to be a const parameter since it's a built-in type, but it's not really a big deal as such uses of const don't hurt. Just wanted to make a note about that.
Prefer size_t for types representing sizes. This can replace every int for such variables, especially the loop counter. You'll get type-matching warnings if your counter type differs from the size type in the loop. In most cases, using int will cause such warnings since it also uses negative numbers.

Just some quick things:

const unsigned int width doesn't need to be const since it's a built-in type, but it's not really a big deal as such uses of const don't hurt. Just wanted to make a note about that.
Prefer size_t for types representing sizes. This can replace every int for such variables, especially the loop counter. You'll get type-matching warnings if your counter type differs from the size type in the loop. In most cases, using int will cause such warnings since it also uses negative numbers.

Just some quick things:

unsigned int width doesn't need to be a const parameter since it's a built-in type, but it's not really a big deal as such uses of const don't hurt. Just wanted to make a note about that.
Prefer size_t for types representing sizes. This can replace every int for such variables, especially the loop counter. You'll get type-matching warnings if your counter type differs from the size type in the loop. In most cases, using int will cause such warnings since it also uses negative numbers.