| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/idlelib/ |
| IOBinding.py | 5 # end-of-line conventions, instead of relying on the standard library,
|
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/ |
| imputil.py | 722 # working given the calling conventions for the __import__ hook: whether
|
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/test/ |
| test_tokenize.py | 68 Some people use different formatting conventions, which makes
|
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/ |
| gettext.py | 294 # See if we're looking at GNU .mo conventions for metadata
|
| imputil.py | 722 # working given the calling conventions for the __import__ hook: whether
|
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/idlelib/ |
| IOBinding.py | 5 # end-of-line conventions, instead of relying on the standard library,
|
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/test/ |
| test_tokenize.py | 68 Some people use different formatting conventions, which makes
|
| /prebuilts/tools/darwin-x86/swt/about_files/ |
| IJG_README | 253 format. For the omitted details we follow the "JFIF" conventions, revision
|
| /prebuilts/tools/darwin-x86_64/swt/about_files/ |
| IJG_README | 253 format. For the omitted details we follow the "JFIF" conventions, revision
|
| /prebuilts/tools/linux-x86/swt/about_files/ |
| IJG_README | 253 format. For the omitted details we follow the "JFIF" conventions, revision
|
| /prebuilts/tools/linux-x86_64/swt/about_files/ |
| IJG_README | 253 format. For the omitted details we follow the "JFIF" conventions, revision
|
| /prebuilts/tools/windows/swt/about_files/ |
| IJG_README | 253 format. For the omitted details we follow the "JFIF" conventions, revision
|
| /prebuilts/tools/windows-x86_64/swt/about_files/ |
| IJG_README | 253 format. For the omitted details we follow the "JFIF" conventions, revision
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/formatting/ |
| AndroidXmlFormattingStrategy.java | 82 * conventions. It performs the format by computing the smallest set of DOM nodes
[all...] |
| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/uimodel/ |
| UiResourceAttributeNode.java | 214 * This works for both "@android:style/foo" and "@style/android:foo" conventions even though
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/wizards/newxmlfile/ |
| AddTranslationDialog.java | 228 // local conventions such as "product=tablet", or "msgid="123123123",
|
| /system/core/adb/ |
| protocol.txt | 116 Common destination naming conventions include:
|
| /test/vts/runners/host/ |
| test_runner.py | 250 # conventions: AaaBbb and aaa_bbb.
|
| /toolchain/binutils/binutils-2.27/bfd/ |
| pei-x86_64.c | 79 /* Name of registers according to SEH conventions. */
|
| /toolchain/binutils/binutils-2.27/gas/doc/ |
| c-alpha.texi | 223 conventions which do not allow the normal call-clobbered registers to be
|
| /toolchain/binutils/binutils-2.27/include/coff/ |
| sym.h | 39 * A brief word about Third Eye naming/use conventions:
|
| /toolchain/binutils/binutils-2.27/zlib/win32/ |
| DLL_FAQ.txt | 184 Anyone interested in different bindings or conventions is
|
| /tools/repohooks/rh/ |
| hooks.py | 396 you to develop conventions that make sense for your project. Note that many
|
| /tools/test/connectivity/acts/framework/acts/ |
| test_runner.py | 183 # conventions: AaaBbb and aaa_bbb.
|
| /external/vulkan-validation-layers/loader/ |
| LoaderAndLayerInterface.md | 24 * [Layer Conventions and Rules](#layer-conventions-and-rules)
[all...] |
