Originally Posted by
JoeTang
I believe it's only bad practice if the pointer name is ambiguous and is used in significantly longer sets of code. Since yours is contextually relevant to what it does, and there's only two lines, it's simple to understand and no confusion should occur about it being reused for a different purpose or the value being changed in such a way that would be difficult to follow by hand.
Correct practice would be to have anything named to be contextually relevant, and simple to read and understand from a third person perspective.