Using Const

• If your function does not modify

parameters, you should declare them as
Intro to C++ part 9 “const”.
• “const” parameters cannot be modified
1. Richard Watson, notes on C++
2. Winston, P.H., “On to C++”
ISBN: 0-201-58043-8

Calling Member Functions This Should Work…

• Sometimes, you need to call member
functions of your const parameters.
• Example: max function for Queues:
Queue Max(const Queue &first, const Queue &second) {
if (first.Size () > second.Size()) {
return first;
} else {
return second;
} doesn’t modify the Queue
}
• But is doesn’t compile
• By declaring “first” and “second” as const,
you promised not to modify them
• The compiler will complain about calling
“Size”
• The compiler doesn’t know that “Size”

Making Class Members Const • Old “Size” prototype:

/* Returns the number of elements in me */
• Class member functions can be declared int Size();

as “const”
• New “Size” prototype:
• Members declared as const cannot modify
fields of the class. /* Returns the number of elements in me */
int Size() const;
• Let’s fix our Size function!
• Definition header changes too:
int Queue::Size() const {
// Algorithm comment:
// n is the size of the queue, return it.
return n;
}

1
 Can’t Go Const Crazy
• Why not declare all functions as “const”?
It would make our lives easier.
• Compiler won’t let you declare a function
as “const” if it modifies any field of the
class.
• Example…
• You *can* change values that are pointed-
to by fields of the class.
• An obvious way around const is to make
all your fields pointers
• But you should not be looking for ways
around const.
• Const is your friend!
Dequeue Can’t Be Const
• Which line(s) keep this from compiling?
char Queue::Dequeue() const {
char head = contents[0];
// shift all elements down 1 slot towards the head.
for(int i = 0; i < n-1; i++) {
contents[i] = contents[i+1];
}
n--; // update size <-- THIS ONE!
return head;
}
The Lesson…
• A member function can be “const” if it
does not modify fields of the class
• Should declare all such members as const
• Although the compiler won’t stop you, you
shouldn’t modify contents of memory that
fields point to in “const” functions.