Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched refs:bltin (Results 1 - 8 of 8) sorted by null

/system/core/sh/
exec.h	49 int (*bltin)(int, char**); member in union:cmdentry::param
exec.c	435 int (*bltin)(int,char **); 497 (bltin = find_builtin(name)) != 0) 517 if ((bltin = find_builtin(name)) == 0) 602 cmdp->param.bltin = bltin; 658 cmdp->param.bltin = bp->builtin; 699 int bltin; local 705 bltin = -1; 716 if (*new == '%' && bltin < 0 && prefix("builtin", new + 1)) 717 bltin = idx     [all...]
Android.mk	29 bltin/echo.c \
eval.c	784 cmdentry.u.bltin = bltincmd; 808 cmdentry.u.bltin != bltincmd) 814 cmdentry.u.bltin = typecmd; 833 || cmdentry.u.bltin == dotcmd 834 || cmdentry.u.bltin == evalcmd))) { 979 mode = (cmdentry.u.bltin == execcmd) ? 0 : REDIR_PUSH; 995 if (path != pathval() && (cmdentry.u.bltin == hashcmd || 996 cmdentry.u.bltin == typecmd)) { 1019 exitstatus = cmdentry.u.bltin(argc, argv); 1046 if (cmdentry.u.bltin != execcmd     [all...]
/ndk/sources/host-tools/nawk-20071023/
proto.h	188 extern Cell *bltin(Node **, int);
run.c	1464 Cell *bltin(Node **a, int n) \/* builtin functions. a[0] is type, a[1] is arg list *\/ function     [all...]
/prebuilts/python/darwin-x86/2.7.5/lib/python2.7/pydoc_data/
topics.py	11 'bltin-code-objects': '\nCode Objects\n************\n\nCode objects are used by the implementation to represent "pseudo-\ncompiled" executable Python code such as a function body. They differ\nfrom function objects because they don\'t contain a reference to their\nglobal execution environment. Code objects are returned by the built-\nin ``compile()`` function and can be extracted from function objects\nthrough their ``func_code`` attribute. See also the ``code`` module.\n\nA code object can be executed or evaluated by passing it (instead of a\nsource string) to the ``exec`` statement or the built-in ``eval()``\nfunction.\n\nSee *The standard type hierarchy* for more information.\n', 12 'bltin-ellipsis-object': '\nThe Ellipsis Object\n*******************\n\nThis object is used by extended slice notation (see *Slicings*). It\nsupports no special operations. There is exactly one ellipsis object,\nnamed ``Ellipsis`` (a built-in name).\n\nIt is written as ``Ellipsis``. When in a subscript, it can also be\nwritten as ``...``, for example ``seq[...]``.\n', 13 'bltin-null-object': "\nThe Null Object\n***************\n\nThis object is returned by functions that don't explicitly return a\nvalue. It supports no special operations. There is exactly one null\nobject, named ``None`` (a built-in name).\n\nIt is written as ``None``.\n", 14 'bltin-type-objects': "\nType Objects\n************\n\nType objects represent the various object types. An object's type is\naccessed by the built-in function ``type()``. There are no special\noperations on types. The standard module ``types`` defines names for\nall standard built-in types.\n\nTypes are written like this: ``<type 'int'>``.\n",     [all...]
/prebuilts/python/linux-x86/2.7.5/lib/python2.7/pydoc_data/
topics.py	11 'bltin-code-objects': '\nCode Objects\n************\n\nCode objects are used by the implementation to represent "pseudo-\ncompiled" executable Python code such as a function body. They differ\nfrom function objects because they don\'t contain a reference to their\nglobal execution environment. Code objects are returned by the built-\nin ``compile()`` function and can be extracted from function objects\nthrough their ``func_code`` attribute. See also the ``code`` module.\n\nA code object can be executed or evaluated by passing it (instead of a\nsource string) to the ``exec`` statement or the built-in ``eval()``\nfunction.\n\nSee *The standard type hierarchy* for more information.\n', 12 'bltin-ellipsis-object': '\nThe Ellipsis Object\n*******************\n\nThis object is used by extended slice notation (see *Slicings*). It\nsupports no special operations. There is exactly one ellipsis object,\nnamed ``Ellipsis`` (a built-in name).\n\nIt is written as ``Ellipsis``. When in a subscript, it can also be\nwritten as ``...``, for example ``seq[...]``.\n', 13 'bltin-null-object': "\nThe Null Object\n***************\n\nThis object is returned by functions that don't explicitly return a\nvalue. It supports no special operations. There is exactly one null\nobject, named ``None`` (a built-in name).\n\nIt is written as ``None``.\n", 14 'bltin-type-objects': "\nType Objects\n************\n\nType objects represent the various object types. An object's type is\naccessed by the built-in function ``type()``. There are no special\noperations on types. The standard module ``types`` defines names for\nall standard built-in types.\n\nTypes are written like this: ``<type 'int'>``.\n",     [all...]

Completed in 242 milliseconds