Well maybe there SHOULD be a way that the method didn't exist in the earlier version. A way that failed at compile time when the user of the api tried to use that CharSequence. What is wrong about having a field in the class definition (version) and the platform having a series of of Interface alterations declared (since version). Then it could raise a error on the client, if he tried to use the method on a compiled api (or even better not show the method).
Is this impossible?
