Lines Matching refs:and
3 %% Purpose: Explains how much and what kind of backward compatibility users
13 Many of the GUIs and platforms supported by wxWidgets are continuously
14 evolving, and some of the new platforms wxWidgets now supports were quite
16 evolve in order to support these new features and platforms.
38 and {\tt 2.6.2} to be backward compatible with their predecessor.
46 The stable branch and the development branch will then be developed in
48 the stable branch, the development branch is renamed and becomes a new
51 This is how the tension between keeping the interface stable, and allowing
54 You can expect the versions with the same major and {\em even} minor
75 Between minor versions, for example between {\tt 2.2.x}, {\tt 2.4.x} and {\tt
93 set them using the {\tt --disable-compat24} and {\tt --enable-compat22}
107 incompatible with some future version of wxWidgets, and you should consider
120 wxWidgets {\tt 2.6.0}, {\tt 2.6.1} and {\tt 2.6.2}. Since {\tt 2.6.2} is
122 install just wxWidgets {\tt 2.6.2} shared libraries, and all the applications
124 the required versions {\tt 2.6.0}, {\tt 2.6.1} and {\tt 2.6.2} must be
128 and recompile everything, places many extra constraints on the changes
130 platforms, and not for all versions of wxWidgets. To date it has mainly
134 all the applications and libraries must have been compiled with compilers
137 compilers do not produce code compatible with each other, and often even
165 depending on a later version of wxWidgets, and also disables any new features
172 and {\em even} minor version numbers. It won't, for example, help you write