## API's that are Subject to Change

Certain Application Programming Interfaces (APIs) documented here are subject to change in future versions of their respective products. The classes and interfaces which are subject to change are identified with a link to this page at the top and bottom of their API documentation (Javadoc) page within the text:

*** This class is subject to change ***

The types of changes include the following.

1. Deprecation of the API
2. Changes in the names of features, including packages, classes, interfaces, methods, and fields
3. Changes in the inheritance relationships of a class or interface
4. Changes in the protection access of classes, interfaces, methods, and fields
5. Changes in method signatures, return types, and/or the set of exceptions which a method is declared to throw
6. Changes in the set of interfaces which a class implements
7. Changes in the `abstract` nature of classes
8. Changes in the behavior of the feature
9. Changes in the serialized format of serializable classes
10. Removal of the API

SAS Institute does not make claims of support or backwards compatibility with APIs which are marked as subject to change. Please bear this in mind if you write software which uses these APIs. You may need to modify your software when SAS Institute releases a new version of these API's. Use of an API includes extending through subclassing or implementing interfaces, instantiation of classes, invocation of methods, and references to fields of a class.

If SAS Institutes makes such changes to these APIs in a future release of the software, SAS Institute will provide guidance in the form of migration documents and release notes.