[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
> My bad :-( I don't think I meant to imply forward binary compatibility,
> rather that forward compatibility may be a nice coincidence of backward
> compatibility.
Well, I read and implicitly approved it so...
I think we have to honor it for the rest of the 4.0.x series, provided that
4.0.2 is still forward binary compatible with 4.0.0, what I'm going to check
today. However, we must not make the same mistake for the 4.2.x series so I'm
proposing the following modifications:
--- /home/eric/cvs/allegro/docs/src/api._tx Fri Nov 29 17:19:18 2002
+++ allegro/docs/src/api._tx Thu Dec 19 08:36:00 2002
@@ -24,17 +24,17 @@
@heading
Introduction
- Once Allegro 4.0 is released, we plan to maintain Application Programming
- Interface compatibility for the rest of the stable releases of the 4.x
- series, that is for the releases with an even minor version number. For
- example, that means you will be able to compile your program written for
- version 4.0 with version 4.0.23 or version 4.2.1 of the library. However,
- in order to fix some minor inconsistencies of the 4.0 API, we may make
- exceptions to the rule and break strict API compatibility in a few cases.
- But this is guaranteed to never happen in a stable series for which major
- and minor version numbers are fixed; in other words, two stable versions
- that differ from each other only by the revision (3rd) number will be
- strictly API compatible.
+ Once Allegro 4.0 is released, we plan to maintain backward compatibility
+ at the Application Programming Interface level for the subsequent stable
+ releases of the 4.x series, that is for the releases with an even minor
+ version number. For example, that means you will be able to compile your
+ program written for version 4.0.0 with version 4.0.23 or version 4.2.1 of
+ the library. However, in order to fix some minor inconsistencies of the
+ original 4.0 API, we may make exceptions to the rule and break strict
+ backward compatibility in a few cases. But this is guaranteed to never
+ happen in a stable series for which major and minor version numbers are
+ fixed; in other words, two stable versions that differ from each other
+ only by the revision (3rd) number will be strictly backward compatible.
@heading
Changes between 4.0.x and 4.2.x series
--- /home/eric/cvs/allegro/docs/src/abi._tx Fri Oct 25 23:25:57 2002
+++ allegro/docs/src/abi._tx Thu Dec 19 08:30:22 2002
@@ -24,10 +24,11 @@
@heading
Introduction
- Once Allegro 4.0 is released, we plan to maintain Application Binary
- Interface compatibility for the rest of the 4.0.x series. For example,
- that means you will be able to use a executable compiled using version
- 4.0.10 with a version 4.0.42 dynamic linker library, or even 4.0.0.
+ Once Allegro 4.2 is released, we plan to maintain backward compatibility
+ at the Application Binary Interface level for the subsequent releases of
+ the 4.2.x series. For example, that means you will be able to use an
+ executable compiled using version 4.2.0 with version 4.2.5 or 4.2.41 of
+ the dynamically linked library.
"Whew," you sigh, "I don't have to put allxxxx.dll in my zips anymore."
--
Eric Botcazou