Why are some data types or functions made Obsolete in a newer version of an API and others are marked as Deprecated? Why not make them all Obsolete or why not make them all Deprecated?
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
closed as not a real question by Jim G., Jesse C. Slicer, MainMa, gnat, Yusubov Oct 17 '12 at 22:30
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.
Deprecation typically serves as a warning that a feature is no longer in favor with the designers of the language. The reasoning for this is one of reverse compatibility. It gives the users of a language time to adjust their code before the language drops those features. It can also serve as a migration path to a new version of a given feature. The feature in question might be retrofitted at some point in the future or rendered obsolete and removed.