HomeSort by relevance Sort by last modified time
    Searched refs:circumstances (Results 1 - 11 of 11) sorted by null

  /external/antlr/runtime/Perl5/lib/ANTLR/
Runtime.pm 89 data types that cannot be handled, performance issues and the circumstances
  /external/mesa3d/docs/specs/
WL_create_wayland_buffer_from_image.spec 87 1) Under what circumstances can the EGL_BAD_MATCH error be generated? Does
MESA_texture_array.spec 43 There are a number of circumstances where an application may wish to
    [all...]
  /external/libunwind/doc/
libunwind-ptrace.tex 58 However, in special circumstances, an application may prefer to use
libunwind.tex 107 special circumstances (e.g., in a signal handler trampoline), even the
  /external/u-boot/dts/
Kconfig 35 In certain circumstances it is necessary to be able to modify
  /external/grpc-grpc/src/csharp/Grpc.Core/
GrpcEnvironment.cs 447 // Under normal circumstances, the user is expected to shutdown all
  /external/kotlinc/
LICENSE     [all...]
NOTICE     [all...]
  /device/linaro/bootloader/edk2/AppPkg/Applications/Python/Python-2.7.10/Lib/pydoc_data/
topics.py 3 topics = {'assert': u'\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 to\n\n if __debug__:\n if not expression1: raise AssertionError(expression2)\n\nThese equivalences assume that "__debug__" and "AssertionError" refer\nto 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 (command\nline option -O). The current code generator emits no code for an\nassert statement when optimization is requested at compile time. Note\nthat it is unnecessary to include the source code for the expression\nthat failed in the error message; it will be displayed as part of the\nstack trace.\n\nAssignments to "__debug__" are illegal. The value for the built-in\nvariable is determined when the interpreter starts.\n',
    [all...]
  /device/linaro/bootloader/edk2/AppPkg/Applications/Python/Python-2.7.2/Lib/pydoc_data/
topics.py 2 topics = {'assert': u'\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...]

Completed in 861 milliseconds