Searched refs:compatibility (Results 1 – 25 of 400) sorted by relevance
12345678910>>...16
31 <U005E> \x01\x33 |3 # R5 compatibility32 <U005E> \x01\x6D |3 # R5 compatibility34 <U0060> \x01\x34 |3 # R5 compatibility36 <U007E> \x01\x31 |3 # R5 compatibility37 <U007E> \x01\x6C |3 # R5 compatibility41 <U00A8> \x01\x30 |3 # R5 compatibility44 <U00B4> \x01\x35 |3 # R5 compatibility113 <U02DA> \x01\x32 |3 # R5 compatibility114 <U02DA> \x01\x44 |3 # R5 compatibility
2 # Obsolete names for backwards compatibility with older users files.25 # For compatibility with MERIT users files.40 # For compatibility with ESVA RADIUS, Old Cistron RADIUS
5 # Use the file 'icuzones' to specify backward compatibility aliases.14 # A simple alias list. We use this to retain backward compatibility.24 #### Aliases that conflict with Olson compatibility Zone definition
10 # in tz.alias for rataining backward compatibility.39 #### Aliases that conflict with Olson compatibility Zone definition
86 dnl aclocal-1.4 backwards compatibility:107 # For backwards non-gettext consistent compatibility...142 dnl aclocal-1.4 backwards compatibility:186 # For backwards non-gettext consistent compatibility...356 dnl aclocal-1.4 backwards compatibility:395 # FIXME: Remove use of undocumented AC_LIST_HEADERS (2.59 compatibility).538 dnl aclocal-1.4 backwards compatibility:561 dnl aclocal-1.4 backwards compatibility:580 dnl aclocal-1.4 backwards compatibility:608 dnl aclocal-1.4 backwards compatibility:[all …]
118 dnl aclocal-1.4 backwards compatibility:154 dnl aclocal-1.4 backwards compatibility:206 dnl aclocal-1.4 backwards compatibility:260 dnl aclocal-1.4 backwards compatibility:317 dnl aclocal-1.4 backwards compatibility:350 dnl aclocal-1.4 backwards compatibility:
117 dnl aclocal-1.4 backwards compatibility:153 dnl aclocal-1.4 backwards compatibility:205 dnl aclocal-1.4 backwards compatibility:259 dnl aclocal-1.4 backwards compatibility:316 dnl aclocal-1.4 backwards compatibility:349 dnl aclocal-1.4 backwards compatibility:
118 dnl aclocal-1.4 backwards compatibility:154 dnl aclocal-1.4 backwards compatibility:206 dnl aclocal-1.4 backwards compatibility:260 dnl aclocal-1.4 backwards compatibility:317 dnl aclocal-1.4 backwards compatibility:365 dnl aclocal-1.4 backwards compatibility:
323 dnl For backward compatibility. Some packages may be using this.346 dnl For backward compatibility. Some configure.ins may be using this.350 dnl For backward compatibility. Some Makefiles may be using this.354 dnl For backward compatibility. Some Makefiles may be using this.358 dnl For backward compatibility. Some Makefiles may be using this.362 dnl For backward compatibility. Some Makefiles may be using this.374 dnl For backward compatibility. Some Makefiles may be using this.
5 table (for backwards compatibility with older kernels, it is also
6 table (for backwards compatibility with older kernels, it is also
303 dnl For backward compatibility. Some packages may be using this.326 dnl For backward compatibility. Some configure.ins may be using this.330 dnl For backward compatibility. Some Makefiles may be using this.334 dnl For backward compatibility. Some Makefiles may be using this.338 dnl For backward compatibility. Some Makefiles may be using this.342 dnl For backward compatibility. Some Makefiles may be using this.354 dnl For backward compatibility. Some Makefiles may be using this.
16 No attempt is made to support runtime compatibility in a shared library17 build. Instead, the API is intended to support backwards compatibility at
4 # Files from the compatibility library
6 * Improved error code compatibility
43 * This downstreaming could have broken bitcode compatibility47 …port for a bunch of obsolete instruction encodings and other backward compatibility hacks. (13 day…53 * We maintain compatibility because Honeycomb SDK is out there.
58 compatibility = 32, enumerator
22 compatibility issue:29 defining _WIN32_WINDOWS to signal Windows 95 compatibility, STLport will
7 When adding ZIP64 support into minizip it would result into risk of breaking compatibility with min…8 All possible work was done for compatibility.
5 To accommodate license compatibility with the widest possible range