Searched full:in (Results 1 – 25 of 709) sorted by relevance
12345678910>>...29
... .h.in platforms/platform_emscripten.h.in platforms/platform_flashplayer.h.in platforms/platform_generic ...
121 # in validate_platform_file()). Fill-ins provide missing optionals.127 # in validate_architecture_file()). Fill-ins provide missing optionals.133 # in validate_compiler_file()). Fill-ins provide missing optionals.136 # filled in with defaults (which are mostly compiler independent), so153 if os.path.isdir(dirname) and '-genconfig' in dirname:165 # in particular a "/* redefine */" comment must remain intact here.190 for line in lines:199 for k in provides.keys():203 for k in requires.keys():207 # for line in stripped_lines: print(line)[all …]
12 * and InputElementRegExp, see E5 Section 7 in its entirety. Note that14 * language (which is explicitly stated in the specification, Section 7.5).22 * operator in "-1.0" is optimized during compilation to yield a single26 * in a continuous range and in a particular order. See genstrings.py.95 /* reserved words: additional future reserved words in strict mode */184 #error mismatch in token defines187 #error mismatch in token defines190 #error mismatch in token defines193 #error mismatch in token defines196 #error mismatch in token defines[all …]
2 * Initialize built-in objects. Current thread must have a valstack42 * Create built-in objects by parsing an init bitstream generated109 #error internal error in defines in duk__duplicate_ram_global_object()160 * more of an issue than having read-only built-in objects (like in duk_hthread_create_builtin_objects()223 * First create all built-in bare objects on the empty valstack. in duk_hthread_create_builtin_objects()225 * Built-ins in the index range [0,DUK_NUM_BUILTINS-1] have value in duk_hthread_create_builtin_objects()228 * Built-ins in the index range [DUK_NUM_BUILTINS,DUK_NUM_ALL_BUILTINS] in duk_hthread_create_builtin_objects()230 * into thr->builtins[]. These are objects referenced in some way in duk_hthread_create_builtin_objects()269 /* Currently all built-in native functions are strict. in duk_hthread_create_builtin_objects()277 /* Built-in 'name' is not writable by default. Function '.name' in duk_hthread_create_builtin_objects()[all …]
2 * Initialize built-in objects. Current thread must have a valstack42 * Create built-in objects by parsing an init bitstream generated109 #error internal error in defines in duk__duplicate_ram_global_object()161 * more of an issue than having read-only built-in objects (like in duk_hthread_create_builtin_objects()224 * First create all built-in bare objects on the empty valstack. in duk_hthread_create_builtin_objects()226 * Built-ins in the index range [0,DUK_NUM_BUILTINS-1] have value in duk_hthread_create_builtin_objects()229 * Built-ins in the index range [DUK_NUM_BUILTINS,DUK_NUM_ALL_BUILTINS] in duk_hthread_create_builtin_objects()231 * into thr->builtins[]. These are objects referenced in some way in duk_hthread_create_builtin_objects()270 /* Currently all built-in native functions are strict. in duk_hthread_create_builtin_objects()278 /* Built-in 'name' is not writable by default. Function '.name' in duk_hthread_create_builtin_objects()[all …]
24 > in the Software without restriction, including without limitation the rights29 > The above copyright notice and this permission notice shall be included in34 > FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE36 > LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,37 > OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN52 > in the Software without restriction, including without limitation the rights57 > The above copyright notice and this permission notice shall be included in62 > FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE64 > LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,65 > OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN[all …]
17 - Fix some bugs/deficiencies in examples and tests20 - Fix include for Lua pages in "Kepler Syntax"53 - Fix misspellings in source code and documentation60 - Provide client peer certificate (X509) in mg\_client\_cert structure74 - Add missing `mg_` or `MG_` to symbols in civetweb.h. Symbols without will be removed a future ver…86 - Ignore leading blank lines in multipart messages (for Android upload service)87 - Rewrite some functions, in particular request parsing88 - CORS preflight directly in the server, with additional config options91 - Allow hostname in listening\_ports96 - Mark "file in memory" feature is a candidate for deletion[all …]
19 Running `CivetWeb` in a terminal, optionally followed by configuration parameters38 If a configuration file is specified explicitly in the command line, i.e.40 Otherwise, CivetWeb will search for the file `CivetWeb.conf` in the same directory that63 but their names are the same as in the config file. All option names are64 listed in the next section. Thus, the following two setups are equivalent:87 ## Pattern matching in configuration options100 All other characters in the pattern match themselves. Examples:109 The following options are supported in `civetweb.c`. They can be used for112 The options are explained in alphabetic order - for a quick start, check124 If set in any other way, the result is unspecified.[all …]
7 … and offers built-in server side Lua, JavaScript and CGI support. Some instructions how to build t…13 There is just a small set of files to compile in to the application,18 The *INL* file extension represents code that is statically included inline in a source file. Slig…41 …y features to the server itself. Several features available in the C interface are missing in the …55 …ample is actively maintained, updated, extended and tested. Other examples in the examples/ folder…73 Not all CivetWeb features available in C are also available in C++.86 CivetWeb is highly customizable at build time, in addition to configuration at start time.89 Start time options are passed to `mg_start`. They are documented in the [UserManual.md](https://git…92 Pointers to callback functions are passed to `mg_start` as well. They are documented in [civetweb.h…95 …in the default can be added by adding a `USE\_<feature>` define. Default features can be removed b…[all …]
28 in mg\_websocket\_write functions. 36 If a websocket connection was used in only one thread, there is37 no incompatibility. If a websocket connection was used in multiple49 was introduced in CivetWeb 1.4 (September 2013).50 Is "file in memory" still a useful feature or dead code? See this52 Since it is not widely used, and a burden in maintenance, the53 "file in memory" should be completely removed, including removing58 Removing "file in memory" will require code using open\_file to be changed.59 A possible replacement by mg\_set\_request\_handler is sketched in70 on the same physical server (same IP+port). In order to support this,[all …]
4 ** The author disclaims copyright to this source code. In place of14 ** or constant definition does not appear in this file, then it is18 ** Some of the definitions that are in this file are marked as22 ** if experience from use "in the wild" suggest such changes are prudent.25 ** from comments in this file. This file is the authoritative source28 ** The name of this file under configuration management is "sqlite.h.in".71 ** These no-op macros are used in front of interfaces to mark those75 ** experimental interfaces are subject to change in point releases.99 ** ^(The [SQLITE_VERSION] C preprocessor macro in the sqlite3.h header100 ** evaluates to a string literal that is the SQLite version in the[all …]
10 ** This file is all you need to compile SQLite. To use SQLite in other17 ** language. The code for the "sqlite3" command-line shell is also in a29 ** The author disclaims copyright to this source code. In place of54 ** for those options in which the value is meaningful. */62 ** This array looks large, but in a typical installation actually uses781 ** The author disclaims copyright to this source code. In place of817 ** In all cases, the special comment must be enclosed in the usual841 ** compiler warnings due to subsequent content in this file and other files844 /************** Include msvc.h in the middle of sqliteInt.h ******************/849 ** The author disclaims copyright to this source code. In place of[all …]
56 the Pontifical Catholic University of Rio de Janeiro in Brazil.59 used in many products and projects around the world.76 distributed in this package.81 Lua is distributed in87 Lua is implemented in pure ANSI C and compiles unmodified in all known107 In most Unix-like platforms, simply do "<KBD>make</KBD>" with a suitable target.128 ansi, in this order.132 and produces three files in the <TT>src</TT> directory:150 Once you have built Lua, you may want to install it in an official151 place in your system. In this case, do "<KBD>make install</KBD>". The official[all …]
51 Lua is implemented as a library, written in <em>clean C</em>,57 it only works <em>embedded</em> in a host client,73 as stated in its license.74 The implementation described in this manual is available80 this document is dry in places.83 For a detailed introduction to programming in Lua,84 see Roberto's book, <em>Programming in Lua</em>.101 There are no type definitions in the language.106 All values in Lua are <em>first-class values</em>.107 This means that all values can be stored in variables,[all …]
55 the Pontifical Catholic University of Rio de Janeiro in Brazil.58 used in many products and projects around the world.75 distributed in this package.79 Lua is distributed in85 Lua is implemented in pure ANSI C and compiles unmodified in all known104 In most Unix-like platforms, simply do "<KBD>make</KBD>" with a suitable target.125 c89, in this order.129 and produces three files in the <TT>src</TT> directory:147 Once you have built Lua, you may want to install it in an official148 place in your system. In this case, do "<KBD>make install</KBD>". The official[all …]
65 Lua is implemented as a library, written in <em>clean C</em>,78 it works <em>embedded</em> in a host client,92 as stated in its license.93 The implementation described in this manual is available99 this document is dry in places.102 For a detailed introduction to programming in Lua,103 see Roberto's book, <em>Programming in Lua</em>.120 There are no type definitions in the language.125 All values in Lua are <em>first-class values</em>.126 This means that all values can be stored in variables,[all …]
53 Lua is implemented as a library, written in <em>clean</em> C54 (that is, in the common subset of ANSI C and C++).59 it only works <em>embedded</em> in a host client,74 as stated in its license.75 The implementation described in this manual is available81 this document is dry in places.84 For a detailed introduction to programming in Lua,85 see Roberto's book, <em>Programming in Lua (Second Edition)</em>.93 In other words,102 in which[all …]
4 ** See Copyright Notice in lua.h19 ** Some notes about garbage-collected objects: All objects in Lua must33 ** in all objects, but it always has this name.) Any gray object34 ** must belong to one of these lists, and all objects in these lists40 ** - black objects got in a write barrier;51 struct lua_longjmp; /* defined in ldo.c */86 ** top function has only the yielded values in its stack; in that87 ** case, the actual 'func' value is saved in field 'extra'.89 ** the function index so that, in case of errors, the continuation93 StkId func; /* function index in the stack */[all …]
4 ** See Copyright Notice in lua.h15 ** Tables keep its elements in two parts: an array part and a hash part.16 ** Non-negative integer keys are all candidates to be kept in the array18 ** more than half the slots between 1 and n are in use.21 ** in its main position (i.e. the 'original' position that its hash gives22 ** to it), then the colliding element is in its own main position.44 ** the largest integer such that MAXASIZE fits in an unsigned int.51 ** integer such that 2^MAXHBITS fits in a signed int. (Note that the52 ** maximum number of elements in a table, 2^MAXABITS + 2^MAXHBITS, still53 ** fits comfortably in an unsigned int.)[all …]
4 ** See Copyright Notice in lua.h31 VK, /* constant in 'k'; info = index of constant in 'k' */34 VNONRELOC, /* expression has its value in a fixed register;37 VUPVAL, /* upvalue variable; info = index of upvalue in 'upvalues' */44 VRELOCABLE, /* expression can put result in any register;73 short idx; /* variable index in stack */80 int pc; /* position in code */82 lu_byte nactvar; /* local level where it appears in current block */89 int n; /* number of entries in use */107 struct BlockCnt; /* defined in lparser.c */[all …]
5 Lua is built in the src directory, but the build process can be14 ansi, in this order.20 after building Lua. Also, have a look at the example programs in test.24 Once you have built Lua, you may want to install it in an official25 place in your system. In this case, do "make install". The official26 place and the way to install files are defined in Makefile. You must29 If you want to build and install Lua in one step, do "make xxx install",43 There are man pages for lua and luac, in both nroff and html, and a44 reference manual in html in doc, some sample code in test, and some45 useful stuff in etc. You don't need these directories for development.[all …]
4 ** See Copyright Notice in lua.h19 ** Some notes about garbage-collected objects: All objects in Lua must22 ** Lua keeps most objects linked in list g->allgc. The link uses field25 ** Strings are kept in several lists headed by the array g->strt.hash.31 ** be remarked in the atomic step. Usually their contents would be marked35 ** Objects with finalizers are kept in the list g->finobj.42 struct lua_longjmp; /* defined in ldo.c */70 StkId func; /* function index in the stack */82 int ctx; /* context info. in case of yields */83 lua_CFunction k; /* continuation in case of yields */[all …]
