| /external/flatbuffers/go/ |
| builder.go | 369 // during the construction of its parent table (between the MyTableBuilder
|
| /external/syzkaller/pkg/ipc/ |
| ipc.go | 81 CallBlocked // finished but blocked during execution
|
| /external/syzkaller/prog/ |
| encoding.go | 111 // Statically typed data will be padded with 0s during
|
| /external/syzkaller/syz-ci/ |
| manager.go | 27 // during that period (or around that period), we can rebuild kernel, restart
|
| /external/v8/benchmarks/ |
| richards.js | 74 "Error during execution: queueCount = " + scheduler.queueCount +
|
| /external/v8/src/js/ |
| array.js | 129 // Global list of arrays visited during toString, toLocaleString and
|
| /external/zlib/src/contrib/masmx64/ |
| gvmat64.asm | 209 ;;; deflate_state structure during the function's setup (before
|
| /external/zlib/src/contrib/masmx86/ |
| match686.asm | 211 ;;; deflate_state structure during the function's setup (before
|
| /build/soong/android/ |
| arch.go | 668 panic(fmt.Errorf("Found Os type duplicate during OsType registration: %q", name))
[all...] |
| /external/clang/tools/scan-build/bin/ |
| scan-build | 1126 during compilation to enable more precise results.
[all...] |
| /external/golang-protobuf/jsonpb/ |
| jsonpb_test.go | [all...] |
| /external/python/cpython3/Lib/ |
| pdb.py | 319 # the current command, so allow them during interactive input
423 """Handles one command line during command list definition."""
[all...] |
| /external/ImageMagick/config/ |
| ltmain.sh | 399 # something went wrong during execution without actually bailing out at
[all...] |
| /external/curl/ |
| ltmain.sh | 399 # something went wrong during execution without actually bailing out at
[all...] |
| /external/expat/conftools/ |
| ltmain.sh | 399 # something went wrong during execution without actually bailing out at
[all...] |
| /external/iperf3/config/ |
| ltmain.sh | 399 # something went wrong during execution without actually bailing out at
[all...] |
| /external/libevent/ |
| ltmain.sh | 399 # something went wrong during execution without actually bailing out at
[all...] |
| /external/libpng/ |
| ltmain.sh | 399 # something went wrong during execution without actually bailing out at
[all...] |
| /external/python/cpython2/Modules/_ctypes/libffi/ |
| ltmain.sh | 289 # something went wrong during execution without actually bailing out at
[all...] |
| /device/linaro/bootloader/edk2/AppPkg/Applications/Python/Python-2.7.2/Lib/pydoc_data/ |
| topics.py | 3 'assignment': u'\nAssignment statements\n*********************\n\nAssignment statements are used to (re)bind names to values and to\nmodify attributes or items of mutable objects:\n\n assignment_stmt ::= (target_list "=")+ (expression_list | yield_expression)\n target_list ::= target ("," target)* [","]\n target ::= identifier\n | "(" target_list ")"\n | "[" target_list "]"\n | attributeref\n | subscription\n | slicing\n\n(See section *Primaries* for the syntax definitions for the last three\nsymbols.)\n\nAn assignment statement evaluates the expression list (remember that\nthis can be a single expression or a comma-separated list, the latter\nyielding a tuple) and assigns the single resulting object to each of\nthe target lists, from left to right.\n\nAssignment is defined recursively depending on the form of the target\n(list). When a target is part of a mutable object (an attribute\nreference, subscription or slicing), the mutable object must\nultimately perform the assignment and decide about its validity, and\nmay raise an exception if the assignment is unacceptable. The rules\nobserved by various types and the exceptions raised are given with the\ndefinition of the object types (see section *The standard type\nhierarchy*).\n\nAssignment of an object to a target list is recursively defined as\nfollows.\n\n* If the target list is a single target: The object is assigned to\n that target.\n\n* If the target list is a comma-separated list of targets: The object\n must be an iterable with the same number of items as there are\n targets in the target list, and the items are assigned, from left to\n right, to the corresponding targets.\n\nAssignment of an object to a single target is recursively defined as\nfollows.\n\n* If the target is an identifier (name):\n\n * If the name does not occur in a ``global`` statement in the\n current code block: the name is bound to the object in the current\n local namespace.\n\n * Otherwise: the name is bound to the object in the current global\n namespace.\n\n The name is rebound if it was already bound. This may cause the\n reference count for the object previously bound to the name to reach\n zero, causing the object to be deallocated and its destructor (if it\n has one) to be called.\n\n* If the target is a target list enclosed in parentheses or in square\n brackets: The object must be an iterable with the same number of\n items as there are targets in the target list, and its items are\n assigned, from left to right, to the corresponding targets.\n\n* If the target is an attribute reference: The primary expression in\n the reference is evaluated. It should yield an object with\n assignable attributes; if this is not the case, ``TypeError`` is\n raised. That object is then asked to assign the assigned object to\n the given attribute; if it cannot perform the assignment, it raises\n an exception (usually but not necessarily ``AttributeError``).\n\n Note: If the object is a class instance and the attribute reference\n occurs on both sides of the assignment operator, the RHS expression,\n ``a.x`` can access either an instance attribute or (if no instance\n attribute exists) a class attribute. The LHS target ``a.x`` is\n always set as an instance attribute, creating it if necessary.\n Thus, the two occurrences of ``a.x`` do not necessarily refer to the\n same attribute: if the RHS expression refers to a class attribute,\n the LHS creates a new instance attribute as the target of the\n assignment:\n\n class Cls:\n x = 3 # class variable\n inst = Cls()\n inst.x = inst.x + 1 # writes inst.x as 4 leaving Cls.x as 3\n\n This description does not necessarily apply to descriptor\n attributes, such as properties created with ``property()``.\n\n* If the target is a subscription: The primary expression in the\n reference is evaluated. It should yield either a mutable sequence\n object (such as a list) or a mapping object (such as a dictionary).\n Next, the subscript expression is evaluated.\n\n If the primary is a mutable sequence object (such as a list), the\n subscript must yield a plain integer. If it is negative, the\n sequence\'s length is added to it. The resulting value must be a\n nonnegative integer less than the sequence\'s length, and the\n sequence is asked to assign the assigned object to its item with\n that index. If the index is out of range, ``IndexError`` is raised\n (assignment to a subscripted sequence cannot add new items to a\n list).\n\n If the primary is a mapping object (such as a dictionary), the\n subscript must have a type compatible with the mapping\'s key type,\n and the mapping is then asked to create a key/datum pair which maps\n the subscript to the assigned object. This can either replace an\n existing key/value pair with the same key value, or insert a new\n key/value pair (if no key with the same value existed).\n\n* If the target is a slicing: The primary expression in the reference\n is evaluated. It should yield a mutable sequence object (such as a\n list). The assigned object should be a sequence object of the same\n type. Next, the lower and upper bound expressions are evaluated,\n insofar they are present; defaults are zero and the sequence\'s\n length. The bounds should evaluate to (small) integers. If either\n bound is negative, the sequence\'s length is added to it. The\n resulting bounds are clipped to lie between zero and the sequence\'s\n length, inclusive. Finally, the sequence object is asked to replace\n the slice with the items of the assigned sequence. The length of\n the slice may be different from the length of the assigned sequence,\n thus changing the length of the target sequence, if the object\n allows it.\n\n**CPython implementation detail:** In the current implementation, the\nsyntax for targets is taken to be the same as for expressions, and\ninvalid syntax is rejected during the code generation phase, causing\nless detailed error messages.\n\nWARNING: Although the definition of assignment implies that overlaps\nbetween the left-hand side and the right-hand side are \'safe\' (for\nexample ``a, b = b, a`` swaps two variables), overlaps *within* the\ncollection of assigned-to variables are not safe! For instance, the\nfollowing program prints ``[0, 2]``:\n\n x = [0, 1]\n i = 0\n i, x[i] = 1, 2\n print x\n\n\nAugmented assignment statements\n===============================\n\nAugmented assignment is the combination, in a single statement, of a\nbinary operation and an assignment statement:\n\n augmented_assignment_stmt ::= augtarget augop (expression_list | yield_expression)\n augtarget ::= identifier | attributeref | subscription | slicing\n augop ::= "+=" | "-=" | "*=" | "/=" | "//=" | "%=" | "**="\n | ">>=" | "<<=" | "&=" | "^=" | "|="\n\n(See section *Primaries* for the syntax definitions for the last three\nsymbols.)\n\nAn augmented assignment evaluates the target (which, unlike normal\nassignment statements, cannot be an unpacking) and the expression\nlist, performs the binary operation specific to the type of assignment\non the two operands, and assigns the result to the original target.\nThe target is only evaluated once.\n\nAn augmented assignment expression like ``x += 1`` can be rewritten as\n``x = x + 1`` to achieve a similar, but not exactly equal effect. In\nthe augmented version, ``x`` is only evaluated once. Also, when\npossible, the actual operation is performed *in-place*, meaning that\nrather than creating a new object and assigning that to the target,\nthe old object is modified instead.\n\nWith the exception of assigning to tuples and multiple targets in a\nsingle statement, the assignment done by augmented assignment\nstatements is handled the same way as normal assignments. Similarly,\nwith the exception of the possible *in-place* behavior, the binary\noperation performed by augmented assignment is the same as the normal\nbinary operations.\n\nFor targets which are attribute references, the same *caveat about\nclass and instance attributes* applies as for regular assignments.\n',
[all...] |
| /external/antlr/runtime/Delphi/Sources/Antlr3.Runtime/ |
| Antlr.Runtime.pas | 408 /// and caches the contents of it's underlying file fully during
545 /// but no token is consumed during recovery...another error is found,
730 /// <summary>A hook to listen in on the token consumption during error recovery.
790 /// is to display just the text, but during development you might
[all...] |
| /external/boringssl/src/ssl/test/runner/ |
| conn.go | 56 // firstFinished contains the first Finished hash sent during the
201 // in any case during testing.
[all...] |
| /external/boringssl/src/util/fipstools/delocate/ |
| delocate.go | 59 // delocation holds the state needed during a delocation operation.
797 // transformation of the data during the process.
[all...] |
| /external/libunwind/aux/ |
| ltmain.sh | 88 # We save the old values to restore during execute mode.
[all...] |
| /external/cmockery/cmockery_0_1_2/ |
| libtool | 292 # Flag to hardcode $libdir into a binary during linking.
297 # a binary during linking. This must work even if $libdir does
304 # Set to yes if using DIR/libNAME during linking hardcodes DIR into the
308 # Set to yes if using the -LDIR flag during linking hardcodes DIR into the
312 # Set to yes if using SHLIBPATH_VAR=DIR during linking hardcodes DIR into
459 # We save the old values to restore during execute mode.
[all...] |
