Printable View
Hi,
I have one question. According to my book it says that placing 'const' in front of the argument of the function generates a compile error if the function attempts to change the arrays' values. Is this only for checking purposes. Coz in some of the functions in my book the 'const' is still used. So i reckon that it's only for checking. Am i right?
thnx
What do you mean by 'checking'?
Maybe they do that in your book, only to be sure of not changing the values in the array.....(to be truly certain of that) and to show for the readers a good way of programming.....but maybe you're right
It's also for optimisation purposes.
For example, the compiler may place the argument you supply into ROM, where it CANNOT be changed. Since you specified const, it means you're not planning on changing it.
Everybody wins.
Downside - you can cast the const away but you shouldn't do that unless you absolutely have to because you need to work with other code somebody's written and they haven't used const, but you know it doesn't change it.