Static variables inside instance methods. How to fix it?

Question

Static variables inside instance methods. How to fix it?

I recently inherited a 10-year code base with some interesting patterns. Among them are static variables inside instance methods. Only one instance of the class is instantiated, and I can hardly find a reason to justify the existence of these static variables in instance methods.

Have you ever developed instance methods with static variables? And what are your rationales?
If this template is considered unsuccessful, then how to fix it?

Note. This question does not apply to Static Variables in Instance Methods

EDIT:

Some reading:

+5

c ++ oop design-patterns static

Viet Aug 10 '12 at 2:42

source share

3 answers

dasblinkenlight · Answer 1 · 2012-08-10T02:46:47+0000

This is a classic C ++ singleton implementation described in one of Scott Meyers C ++ books.
Singleton is a controversial template , so there is no consensus that the monophonic approach is weak or weak.

An alternative to singleton is purely static objects. This question has a good discussion.

chrisduran · Answer 2 · 2012-08-10T02:51:31+0000

About the only time when I used static fields in an unstable class was constant.

, , , (, , ). . , , - .

VoidStar · Answer 3 · 2012-08-10T03:38:39+0000

, .

, - , , -, . , , , .

Static variables inside instance methods. How to fix it?

EDIT:

More articles: