1. Backward compatible changes cause the number to increment.

2. In this case however, the change is not backward compatible as the existing consumers using the withdraw operation are broken because they will not be invoking authorize.

3. Currently, there is no specification for developing backward compatible EJB stubs and ties.

4. Table 1 compares costs between making backward compatible changes and backward incompatible changes that employ versioning.

5. You can also mount an ext4 file system as ext3 (backward compatible)(), but only if the ext4 file system does not use extents (which is discussed in the performance section).

6. Finally, a solution must be backward compatible with the original schema.

7. Ext4 is both forward and backward compatible (meaning that you can mount an ext4 file system on an ext3 disk format and vice versa, depending upon the features used).

8. Keeping styles backward compatible can be a problem -- particularly if you're using complex style with class variants.

9. This results in a backward compatible change to the Web service, which allows both the old and new version of the operation to coexist.

10. Message reflection is backward compatible with code written for versions of MFC previous to 4.0.

11. To be minor, a change must be backward compatible, meaning that old clients can still talk with your new web service.

12. I don't address those topics here; instead, I focus on the set of changes which you can make to an existing service so that it remains backward compatible with older clients.

13. Changes to message formats can be made so that they are backward compatible, that is, so that existing code does not have to be updated.

13.

14. Changes in such a central library can easily render a system useless if such changes are not backward compatible.

15. According to our previous discussion, this change would be backward compatible.

16. The table above indicates that backward incompatible changes with versioning are more expensive than backward compatible changes.

17. Above, this article described the UPDATE XMLSCHEMA command to store updated — and backward compatible — versions of a schema in the XSR.

18. Several papers have been published on the subject of classification of backward compatible versus backward incompatible changes (See Resources).

19. If existing users are unaffected then the change is backward compatible.

20. As a service provider, the approach allows you to support change that is not backward compatible in a sustainable way, without the need to carry on supporting the old interface indefinitely.

21. From the outset, we were clear that Spring 2.0 was going to be fully backward compatible, or as near to fully backward compatible as possible.