RubyGems - Tamar - Versions diffs - 0.7.5 → 0.7.6 - Mend

Tamar 0.7.5 → 0.7.6

Files changed (118) hide show

data/.gitmodules +3 -0
data/HISTORY +22 -5
data/Tamar.gemspec +114 -1
data/VERSION +1 -1
data/src/lua/CMakeLists.txt +176 -0
data/src/lua/COPYRIGHT +34 -0
data/src/lua/FindReadline.cmake +25 -0
data/src/lua/HISTORY +183 -0
data/src/lua/INSTALL +99 -0
data/src/lua/Makefile +128 -0
data/src/lua/README +46 -0
data/src/lua/dist.cmake +450 -0
data/src/lua/dist.info +10 -0
data/src/lua/doc/amazon.gif +0 -0
data/src/lua/doc/contents.html +499 -0
data/src/lua/doc/cover.png +0 -0
data/src/lua/doc/logo.gif +0 -0
data/src/lua/doc/lua.1 +163 -0
data/src/lua/doc/lua.css +41 -0
data/src/lua/doc/lua.html +172 -0
data/src/lua/doc/luac.1 +136 -0
data/src/lua/doc/luac.html +145 -0
data/src/lua/doc/manual.css +13 -0
data/src/lua/doc/manual.html +8801 -0
data/src/lua/doc/readme.html +40 -0
data/src/lua/etc/Makefile +44 -0
data/src/lua/etc/README +37 -0
data/src/lua/etc/all.c +38 -0
data/src/lua/etc/lua.hpp +9 -0
data/src/lua/etc/lua.ico +0 -0
data/src/lua/etc/lua.pc +31 -0
data/src/lua/etc/luavs.bat +28 -0
data/src/lua/etc/min.c +39 -0
data/src/lua/etc/noparser.c +50 -0
data/src/lua/etc/strict.lua +41 -0
data/src/lua/src/Makefile +182 -0
data/src/lua/src/lapi.c +1087 -0
data/src/lua/src/lapi.h +16 -0
data/src/lua/src/lauxlib.c +652 -0
data/src/lua/src/lauxlib.h +174 -0
data/src/lua/src/lbaselib.c +653 -0
data/src/lua/src/lcode.c +831 -0
data/src/lua/src/lcode.h +76 -0
data/src/lua/src/ldblib.c +398 -0
data/src/lua/src/ldebug.c +638 -0
data/src/lua/src/ldebug.h +33 -0
data/src/lua/src/ldo.c +518 -0
data/src/lua/src/ldo.h +57 -0
data/src/lua/src/ldump.c +164 -0
data/src/lua/src/lfunc.c +174 -0
data/src/lua/src/lfunc.h +34 -0
data/src/lua/src/lgc.c +711 -0
data/src/lua/src/lgc.h +110 -0
data/src/lua/src/linit.c +38 -0
data/src/lua/src/liolib.c +556 -0
data/src/lua/src/llex.c +463 -0
data/src/lua/src/llex.h +81 -0
data/src/lua/src/llimits.h +128 -0
data/src/lua/src/lmathlib.c +263 -0
data/src/lua/src/lmem.c +86 -0
data/src/lua/src/lmem.h +49 -0
data/src/lua/src/loadlib.c +666 -0
data/src/lua/src/loadlib_rel.c +719 -0
data/src/lua/src/lobject.c +214 -0
data/src/lua/src/lobject.h +381 -0
data/src/lua/src/lopcodes.c +102 -0
data/src/lua/src/lopcodes.h +268 -0
data/src/lua/src/loslib.c +243 -0
data/src/lua/src/lparser.c +1339 -0
data/src/lua/src/lparser.h +82 -0
data/src/lua/src/lstate.c +214 -0
data/src/lua/src/lstate.h +169 -0
data/src/lua/src/lstring.c +111 -0
data/src/lua/src/lstring.h +31 -0
data/src/lua/src/lstrlib.c +871 -0
data/src/lua/src/ltable.c +588 -0
data/src/lua/src/ltable.h +40 -0
data/src/lua/src/ltablib.c +287 -0
data/src/lua/src/ltm.c +75 -0
data/src/lua/src/ltm.h +54 -0
data/src/lua/src/lua.c +392 -0
data/src/lua/src/lua.def +131 -0
data/src/lua/src/lua.h +388 -0
data/src/lua/src/lua.rc +28 -0
data/src/lua/src/lua_dll.rc +26 -0
data/src/lua/src/luac.c +200 -0
data/src/lua/src/luac.rc +1 -0
data/src/lua/src/luaconf.h.in +724 -0
data/src/lua/src/luaconf.h.orig +763 -0
data/src/lua/src/lualib.h +53 -0
data/src/lua/src/lundump.c +227 -0
data/src/lua/src/lundump.h +36 -0
data/src/lua/src/lvm.c +766 -0
data/src/lua/src/lvm.h +36 -0
data/src/lua/src/lzio.c +82 -0
data/src/lua/src/lzio.h +67 -0
data/src/lua/src/print.c +227 -0
data/src/lua/test/README +26 -0
data/src/lua/test/bisect.lua +27 -0
data/src/lua/test/cf.lua +16 -0
data/src/lua/test/echo.lua +5 -0
data/src/lua/test/env.lua +7 -0
data/src/lua/test/factorial.lua +32 -0
data/src/lua/test/fib.lua +40 -0
data/src/lua/test/fibfor.lua +13 -0
data/src/lua/test/globals.lua +13 -0
data/src/lua/test/hello.lua +3 -0
data/src/lua/test/life.lua +111 -0
data/src/lua/test/luac.lua +7 -0
data/src/lua/test/printf.lua +7 -0
data/src/lua/test/readonly.lua +12 -0
data/src/lua/test/sieve.lua +29 -0
data/src/lua/test/sort.lua +66 -0
data/src/lua/test/table.lua +12 -0
data/src/lua/test/trace-calls.lua +32 -0
data/src/lua/test/trace-globals.lua +38 -0
data/src/lua/test/xd.lua +14 -0
metadata +115 -2

data/src/lua/doc/lua.css ADDED Viewed

@@ -0,0 +1,41 @@
+body {
+	color: #000000 ;
+	background-color: #FFFFFF ;
+	font-family: sans-serif ;
+	text-align: justify ;
+	margin-right: 20px ;
+	margin-left: 20px ;
+}
+h1, h2, h3, h4 {
+	font-weight: normal ;
+	font-style: italic ;
+}
+a:link {
+	color: #000080 ;
+	background-color: inherit ;
+	text-decoration: none ;
+}
+a:visited {
+	background-color: inherit ;
+	text-decoration: none ;
+}
+a:link:hover, a:visited:hover {
+	color: #000080 ;
+	background-color: #E0E0FF ;
+}
+a:link:active, a:visited:active {
+	color: #FF0000 ;
+}
+hr {
+	border: 0 ;
+	height: 1px ;
+	color: #a0a0a0 ;
+	background-color: #a0a0a0 ;
+}

data/src/lua/doc/lua.html ADDED Viewed

@@ -0,0 +1,172 @@
+<!-- $Id: lua.man,v 1.11 2006/01/06 16:03:34 lhf Exp $ -->
+<HTML>
+<HEAD>
+<TITLE>LUA man page</TITLE>
+<LINK REL="stylesheet" TYPE="text/css" HREF="lua.css">
+</HEAD>
+<BODY BGCOLOR="#FFFFFF">
+<H2>NAME</H2>
+lua - Lua interpreter
+<H2>SYNOPSIS</H2>
+<B>lua</B>
+[
+<I>options</I>
+]
+[
+<I>script</I>
+[
+<I>args</I>
+]
+]
+<H2>DESCRIPTION</H2>
+<B>lua</B>
+is the stand-alone Lua interpreter.
+It loads and executes Lua programs,
+either in textual source form or
+in precompiled binary form.
+(Precompiled binaries are output by
+<B>luac</B>,
+the Lua compiler.)
+<B>lua</B>
+can be used as a batch interpreter and also interactively.
+<P>
+The given
+<I>options</I>
+(see below)
+are executed and then
+the Lua program in file
+<I>script</I>
+is loaded and executed.
+The given
+<I>args</I>
+are available to
+<I>script</I>
+as strings in a global table named
+<B>arg</B>.
+If these arguments contain spaces or other characters special to the shell,
+then they should be quoted
+(but note that the quotes will be removed by the shell).
+The arguments in
+<B>arg</B>
+start at 0,
+which contains the string
+'<I>script</I>'.
+The index of the last argument is stored in
+<B>arg.n</B>.
+The arguments given in the command line before
+<I>script</I>,
+including the name of the interpreter,
+are available in negative indices in
+<B>arg</B>.
+<P>
+At the very start,
+before even handling the command line,
+<B>lua</B>
+executes the contents of the environment variable
+<B>LUA_INIT</B>,
+if it is defined.
+If the value of
+<B>LUA_INIT</B>
+is of the form
+'@<I>filename</I>',
+then
+<I>filename</I>
+is executed.
+Otherwise, the string is assumed to be a Lua statement and is executed.
+<P>
+Options start with
+<B>'-'</B>
+and are described below.
+You can use
+<B>'--'</B>
+to signal the end of options.
+<P>
+If no arguments are given,
+then
+<B>"-v -i"</B>
+is assumed when the standard input is a terminal;
+otherwise,
+<B>"-"</B>
+is assumed.
+<P>
+In interactive mode,
+<B>lua</B>
+prompts the user,
+reads lines from the standard input,
+and executes them as they are read.
+If a line does not contain a complete statement,
+then a secondary prompt is displayed and
+lines are read until a complete statement is formed or
+a syntax error is found.
+So, one way to interrupt the reading of an incomplete statement is
+to force a syntax error:
+adding a
+<B>';'</B>
+in the middle of a statement is a sure way of forcing a syntax error
+(except inside multiline strings and comments; these must be closed explicitly).
+If a line starts with
+<B>'='</B>,
+then
+<B>lua</B>
+displays the values of all the expressions in the remainder of the
+line. The expressions must be separated by commas.
+The primary prompt is the value of the global variable
+<B>_PROMPT</B>,
+if this value is a string;
+otherwise, the default prompt is used.
+Similarly, the secondary prompt is the value of the global variable
+<B>_PROMPT2</B>.
+So,
+to change the prompts,
+set the corresponding variable to a string of your choice.
+You can do that after calling the interpreter
+or on the command line
+(but in this case you have to be careful with quotes
+if the prompt string contains a space; otherwise you may confuse the shell.)
+The default prompts are "&gt; " and "&gt;&gt; ".
+<H2>OPTIONS</H2>
+<P>
+<B>-</B>
+load and execute the standard input as a file,
+that is,
+not interactively,
+even when the standard input is a terminal.
+<P>
+<B>-e </B><I>stat</I>
+execute statement
+<I>stat</I>.
+You need to quote
+<I>stat </I>
+if it contains spaces, quotes,
+or other characters special to the shell.
+<P>
+<B>-i</B>
+enter interactive mode after
+<I>script</I>
+is executed.
+<P>
+<B>-l </B><I>name</I>
+call
+<B>require</B>('<I>name</I>')
+before executing
+<I>script</I>.
+Typically used to load libraries.
+<P>
+<B>-v</B>
+show version information.
+<H2>SEE ALSO</H2>
+<B>luac</B>(1)
+<BR>
+<A HREF="http://www.lua.org/">http://www.lua.org/</A>
+<H2>DIAGNOSTICS</H2>
+Error messages should be self explanatory.
+<H2>AUTHORS</H2>
+R. Ierusalimschy,
+L. H. de Figueiredo,
+and
+W. Celes
+<!-- EOF -->
+</BODY>
+</HTML>

data/src/lua/doc/luac.1 ADDED Viewed

@@ -0,0 +1,136 @@
+.\" $Id: luac.man,v 1.28 2006/01/06 16:03:34 lhf Exp $
+.TH LUAC 1 "$Date: 2006/01/06 16:03:34 $"
+.SH NAME
+luac \- Lua compiler
+.SH SYNOPSIS
+.B luac
+[
+.I options
+] [
+.I filenames
+]
+.SH DESCRIPTION
+.B luac
+is the Lua compiler.
+It translates programs written in the Lua programming language
+into binary files that can be later loaded and executed.
+.LP
+The main advantages of precompiling chunks are:
+faster loading,
+protecting source code from accidental user changes,
+and
+off-line syntax checking.
+.LP
+Pre-compiling does not imply faster execution
+because in Lua chunks are always compiled into bytecodes before being executed.
+.B luac
+simply allows those bytecodes to be saved in a file for later execution.
+.LP
+Pre-compiled chunks are not necessarily smaller than the corresponding source.
+The main goal in pre-compiling is faster loading.
+.LP
+The binary files created by
+.B luac
+are portable only among architectures with the same word size and byte order.
+.LP
+.B luac
+produces a single output file containing the bytecodes
+for all source files given.
+By default,
+the output file is named
+.BR luac.out ,
+but you can change this with the
+.B \-o
+option.
+.LP
+In the command line,
+you can mix
+text files containing Lua source and
+binary files containing precompiled chunks.
+This is useful to combine several precompiled chunks,
+even from different (but compatible) platforms,
+into a single precompiled chunk.
+.LP
+You can use
+.B "'\-'"
+to indicate the standard input as a source file
+and
+.B "'\--'"
+to signal the end of options
+(that is,
+all remaining arguments will be treated as files even if they start with
+.BR "'\-'" ).
+.LP
+The internal format of the binary files produced by
+.B luac
+is likely to change when a new version of Lua is released.
+So,
+save the source files of all Lua programs that you precompile.
+.LP
+.SH OPTIONS
+Options must be separate.
+.TP
+.B \-l
+produce a listing of the compiled bytecode for Lua's virtual machine.
+Listing bytecodes is useful to learn about Lua's virtual machine.
+If no files are given, then
+.B luac
+loads
+.B luac.out
+and lists its contents.
+.TP
+.BI \-o " file"
+output to
+.IR file ,
+instead of the default
+.BR luac.out .
+(You can use
+.B "'\-'"
+for standard output,
+but not on platforms that open standard output in text mode.)
+The output file may be a source file because
+all files are loaded before the output file is written.
+Be careful not to overwrite precious files.
+.TP
+.B \-p
+load files but do not generate any output file.
+Used mainly for syntax checking and for testing precompiled chunks:
+corrupted files will probably generate errors when loaded.
+Lua always performs a thorough integrity test on precompiled chunks.
+Bytecode that passes this test is completely safe,
+in the sense that it will not break the interpreter.
+However,
+there is no guarantee that such code does anything sensible.
+(None can be given, because the halting problem is unsolvable.)
+If no files are given, then
+.B luac
+loads
+.B luac.out
+and tests its contents.
+No messages are displayed if the file passes the integrity test.
+.TP
+.B \-s
+strip debug information before writing the output file.
+This saves some space in very large chunks,
+but if errors occur when running a stripped chunk,
+then the error messages may not contain the full information they usually do.
+For instance,
+line numbers and names of local variables are lost.
+.TP
+.B \-v
+show version information.
+.SH FILES
+.TP 15
+.B luac.out
+default output file
+.SH "SEE ALSO"
+.BR lua (1)
+.br
+http://www.lua.org/
+.SH DIAGNOSTICS
+Error messages should be self explanatory.
+.SH AUTHORS
+L. H. de Figueiredo,
+R. Ierusalimschy and
+W. Celes
+.\" EOF

data/src/lua/doc/luac.html ADDED Viewed

@@ -0,0 +1,145 @@
+<!-- $Id: luac.man,v 1.28 2006/01/06 16:03:34 lhf Exp $ -->
+<HTML>
+<HEAD>
+<TITLE>LUAC man page</TITLE>
+<LINK REL="stylesheet" TYPE="text/css" HREF="lua.css">
+</HEAD>
+<BODY BGCOLOR="#FFFFFF">
+<H2>NAME</H2>
+luac - Lua compiler
+<H2>SYNOPSIS</H2>
+<B>luac</B>
+[
+<I>options</I>
+] [
+<I>filenames</I>
+]
+<H2>DESCRIPTION</H2>
+<B>luac</B>
+is the Lua compiler.
+It translates programs written in the Lua programming language
+into binary files that can be later loaded and executed.
+<P>
+The main advantages of precompiling chunks are:
+faster loading,
+protecting source code from accidental user changes,
+and
+off-line syntax checking.
+<P>
+Precompiling does not imply faster execution
+because in Lua chunks are always compiled into bytecodes before being executed.
+<B>luac</B>
+simply allows those bytecodes to be saved in a file for later execution.
+<P>
+Precompiled chunks are not necessarily smaller than the corresponding source.
+The main goal in precompiling is faster loading.
+<P>
+The binary files created by
+<B>luac</B>
+are portable only among architectures with the same word size and byte order.
+<P>
+<B>luac</B>
+produces a single output file containing the bytecodes
+for all source files given.
+By default,
+the output file is named
+<B>luac.out</B>,
+but you can change this with the
+<B>-o</B>
+option.
+<P>
+In the command line,
+you can mix
+text files containing Lua source and
+binary files containing precompiled chunks.
+This is useful because several precompiled chunks,
+even from different (but compatible) platforms,
+can be combined into a single precompiled chunk.
+<P>
+You can use
+<B>'-'</B>
+to indicate the standard input as a source file
+and
+<B>'--'</B>
+to signal the end of options
+(that is,
+all remaining arguments will be treated as files even if they start with
+<B>'-'</B>).
+<P>
+The internal format of the binary files produced by
+<B>luac</B>
+is likely to change when a new version of Lua is released.
+So,
+save the source files of all Lua programs that you precompile.
+<P>
+<H2>OPTIONS</H2>
+Options must be separate.
+<P>
+<B>-l</B>
+produce a listing of the compiled bytecode for Lua's virtual machine.
+Listing bytecodes is useful to learn about Lua's virtual machine.
+If no files are given, then
+<B>luac</B>
+loads
+<B>luac.out</B>
+and lists its contents.
+<P>
+<B>-o </B><I>file</I>
+output to
+<I>file</I>,
+instead of the default
+<B>luac.out</B>.
+(You can use
+<B>'-'</B>
+for standard output,
+but not on platforms that open standard output in text mode.)
+The output file may be a source file because
+all files are loaded before the output file is written.
+Be careful not to overwrite precious files.
+<P>
+<B>-p</B>
+load files but do not generate any output file.
+Used mainly for syntax checking and for testing precompiled chunks:
+corrupted files will probably generate errors when loaded.
+Lua always performs a thorough integrity test on precompiled chunks.
+Bytecode that passes this test is completely safe,
+in the sense that it will not break the interpreter.
+However,
+there is no guarantee that such code does anything sensible.
+(None can be given, because the halting problem is unsolvable.)
+If no files are given, then
+<B>luac</B>
+loads
+<B>luac.out</B>
+and tests its contents.
+No messages are displayed if the file passes the integrity test.
+<P>
+<B>-s</B>
+strip debug information before writing the output file.
+This saves some space in very large chunks,
+but if errors occur when running a stripped chunk,
+then the error messages may not contain the full information they usually do.
+For instance,
+line numbers and names of local variables are lost.
+<P>
+<B>-v</B>
+show version information.
+<H2>FILES</H2>
+<P>
+<B>luac.out</B>
+default output file
+<H2>SEE ALSO</H2>
+<B>lua</B>(1)
+<BR>
+<A HREF="http://www.lua.org/">http://www.lua.org/</A>
+<H2>DIAGNOSTICS</H2>
+Error messages should be self explanatory.
+<H2>AUTHORS</H2>
+L. H. de Figueiredo,
+R. Ierusalimschy and
+W. Celes
+<!-- EOF -->
+</BODY>
+</HTML>

data/src/lua/doc/manual.css ADDED Viewed

@@ -0,0 +1,13 @@
+h3 code {
+	font-family: inherit ;
+}
+pre {
+	font-size: 105% ;
+}
+span.apii {
+	float: right ;
+	font-family: inherit ;
+}