Question

T *p = new T();

For the pointer on heap, there can be disastrous operations such as,

p++;  // (1) scope missed
p = new T(); // (2) re-assignment

Which would result in memory leaks or crashes due to wrong delete. Apart from using smart pointers, is it advisable always to make heap pointer a const;

T* const p = new T();  // now "p" is not modifiable

This question is in regards of maintaining good programming practice and coding style.

Answer 1

I hesitate to say always, but what you propose seems reasonable for many/most cases. Const correctness is something most C++ folks pay a fair bit of attention to in function parameters, but not so much in local (or even member) variables. We might be better off to do so.