||Seven Low-Cost Ways to Improve Legacy Code|
|Subject:||Re: 5: Removing Anonymous Inner Classes|
|From:||Robert Simmons Jr. (Kraythe)|
Response to: Re: 5: Removing Anonymous Inner Classes
I would disagree with declaring a class that can be used only once on general OO design principles. You may dislike the IF structure but actually you are incurring massive overhead in the class declaration in order to avoid the if structure. In addition, the special access rules for anonymous classes makes them often difficult to manage and debug.
Hear us Roar