Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched full:unnecessary (Results 1401 - 1411 of 1411) sorted by null

<<51525354555657

/prebuilts/gcc/darwin-x86/arm/arm-eabi-4.6/share/info/
gccint.info	[all...]
gdb.info	[all...]
/prebuilts/gcc/darwin-x86/arm/arm-linux-androideabi-4.6/share/info/
gccint.info	[all...]
gdb.info	[all...]
/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/share/info/
gccint.info	[all...]
gdb.info	[all...]
/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/share/info/
gccint.info	[all...]
gdb.info	[all...]
/prebuilts/python/darwin-x86/2.7.5/lib/python2.7/pydoc_data/
topics.py	2 topics = {'assert': '\nThe ``assert`` statement\n************************\n\nAssert statements are a convenient way to insert debugging assertions\ninto a program:\n\n assert_stmt ::= "assert" expression ["," expression]\n\nThe simple form, ``assert expression``, is equivalent to\n\n if __debug__:\n if not expression: raise AssertionError\n\nThe extended form, ``assert expression1, expression2``, is equivalent\nto\n\n if __debug__:\n if not expression1: raise AssertionError(expression2)\n\nThese equivalences assume that ``__debug__`` and ``AssertionError``\nrefer to the built-in variables with those names. In the current\nimplementation, the built-in variable ``__debug__`` is ``True`` under\nnormal circumstances, ``False`` when optimization is requested\n(command line option -O). The current code generator emits no code\nfor an assert statement when optimization is requested at compile\ntime. Note that it is unnecessary to include the source code for the\nexpression that failed in the error message; it will be displayed as\npart of the stack trace.\n\nAssignments to ``__debug__`` are illegal. The value for the built-in\nvariable is determined when the interpreter starts.\n',     [all...]
/prebuilts/python/linux-x86/2.7.5/lib/python2.7/pydoc_data/
topics.py	2 topics = {'assert': '\nThe ``assert`` statement\n************************\n\nAssert statements are a convenient way to insert debugging assertions\ninto a program:\n\n assert_stmt ::= "assert" expression ["," expression]\n\nThe simple form, ``assert expression``, is equivalent to\n\n if __debug__:\n if not expression: raise AssertionError\n\nThe extended form, ``assert expression1, expression2``, is equivalent\nto\n\n if __debug__:\n if not expression1: raise AssertionError(expression2)\n\nThese equivalences assume that ``__debug__`` and ``AssertionError``\nrefer to the built-in variables with those names. In the current\nimplementation, the built-in variable ``__debug__`` is ``True`` under\nnormal circumstances, ``False`` when optimization is requested\n(command line option -O). The current code generator emits no code\nfor an assert statement when optimization is requested at compile\ntime. Note that it is unnecessary to include the source code for the\nexpression that failed in the error message; it will be displayed as\npart of the stack trace.\n\nAssignments to ``__debug__`` are illegal. The value for the built-in\nvariable is determined when the interpreter starts.\n',     [all...]
/prebuilts/tools/common/m2/internal/xerces/xercesImpl/2.6.2/
xercesImpl-2.6.2.jar

Completed in 155 milliseconds

<<51525354555657