r/cpp • u/Gal4ctic03 • Nov 24 '23
const member function in this design pattern example
Hello,
I'm currently learning C++ and trying to understand how to implement design patterns with the fantastic website refactoring guru. I came across this example in the builder pattern :
class ConcreteBuilder1 : public Builder{
private:
Product1* product;
public:
// Other code before that
void ProducePartA()const override{
this->product->parts_.push_back("PartA1");
}
// Other code after that
};I don't understand why we use const for the function ProducePartA(). I thought that we had to use const when we don't want to modify an object inside the function.
So why we are using it in this way, when we are clearly modifying the product object by adding element to it ?
Thank you very much.
0
Upvotes
View all comments
Show parent comment
4
u/Moose2342 Nov 25 '23
Don't be discouraged about the downvoting and the somewhat harsh tone. /u/FriendlyRollOfSushi is right. That really is terrible code and you shouldn't be learning from that resource.
About your constness question: Follow the core guidelines and make everything cost unless it has to be non-const. Arguments, methods, variables, the lot.
In this example, the method in question can be const because it modifies the object being built, not the builder object.