>Code replacement on that scale is not possible for this application, or it would have been done already. This is a large, commercial application with a development schedule planned out years in advance. This particular cursor is referenced by name in many places and, no matter how much a change would be cleaner, it simply cannot be done in the short term.
Yeah, I guess it can be difficult.
But one thing is not quite clear to me: If you decide to clean up the cursor after so-and-so-many replacements, don't you need to do this change in hundreds of places as well?
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
