wikimedia/mediawiki-extensions-Scribunto
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/extensions/Scribunto synced 2024-11-16 04:15:48 +00:00
Code Issues Packages Projects Releases Wiki Activity
mediawiki-extensions-Scribunto/engines/LuaStandalone/binaries/README

38 lines
1.9 KiB
Plaintext
Raw Normal View History

Add comments and remove trailing whitespace Clean up trailing whitespace from all of our code, and add comments indicating that apparently unused variables are ScopedCallbacks. Change-Id: I8e5997797cc7b1c64c5351ec112a18f30edc8fef
2014-07-07 18:46:59 +00:00
The Windows binaries are from http://luabinaries.sourceforge.net/ . The C
runtime libraries for Visual C++ 8 are required, and are not bundled. If an
Introduced standalone interpreter, implemented module isolation * Introduced a Lua implementation based on shelling out to a standard Lua binary. * Bundled several Lua binaries for common platforms. I haven't added a 32-bit Linux binary yet, but that will come. * Refactored the existing Lua class, bringing out functionality common to all Lua implementations into a set of common base classes. * Moved the bulk of the implementation-specific functionality into a set of "interpreter" classes. * Renamed LuaSandboxEngine to Scribunto_LuaSandboxEngine * Don't create an engine object unconditionally when the ParserLimitReport hook is called. * Implemented isolation of module global variable namespaces. This means that separate {{#invoke}} calls can't pass data to each other -- this was a desired feature in planning since it allows more flexibility in wikitext parser design. Isolation for mw.import() means that modules cannot accidentally create global variables which affect other modules -- exports are solely via the return value. Change-Id: I3fa35651fe5b1fbfd85adeadc220b1ea31cd6f0b
2012-04-13 10:38:12 +00:00
error is seen reporting that "msvcr80.dll" is not present, it can be downloaded
from Microsoft:
* 32-bit: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5638
* 64-bit: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=21254
Add comments and remove trailing whitespace Clean up trailing whitespace from all of our code, and add comments indicating that apparently unused variables are ScopedCallbacks. Change-Id: I8e5997797cc7b1c64c5351ec112a18f30edc8fef
2014-07-07 18:46:59 +00:00
The Linux binaries were compiled using "make generic". Lua does not use
Introduced standalone interpreter, implemented module isolation * Introduced a Lua implementation based on shelling out to a standard Lua binary. * Bundled several Lua binaries for common platforms. I haven't added a 32-bit Linux binary yet, but that will come. * Refactored the existing Lua class, bringing out functionality common to all Lua implementations into a set of common base classes. * Moved the bulk of the implementation-specific functionality into a set of "interpreter" classes. * Renamed LuaSandboxEngine to Scribunto_LuaSandboxEngine * Don't create an engine object unconditionally when the ParserLimitReport hook is called. * Implemented isolation of module global variable namespaces. This means that separate {{#invoke}} calls can't pass data to each other -- this was a desired feature in planning since it allows more flexibility in wikitext parser design. Isolation for mw.import() means that modules cannot accidentally create global variables which affect other modules -- exports are solely via the return value. Change-Id: I3fa35651fe5b1fbfd85adeadc220b1ea31cd6f0b
2012-04-13 10:38:12 +00:00
autoconf, rather it encourages users to edit the makefile. The makefile patch
used to create the Linux binaries is in generic.patch.
Add comments and remove trailing whitespace Clean up trailing whitespace from all of our code, and add comments indicating that apparently unused variables are ScopedCallbacks. Change-Id: I8e5997797cc7b1c64c5351ec112a18f30edc8fef
2014-07-07 18:46:59 +00:00
Compiling with "make generic" avoids introducing dynamic library dependencies
Introduced standalone interpreter, implemented module isolation * Introduced a Lua implementation based on shelling out to a standard Lua binary. * Bundled several Lua binaries for common platforms. I haven't added a 32-bit Linux binary yet, but that will come. * Refactored the existing Lua class, bringing out functionality common to all Lua implementations into a set of common base classes. * Moved the bulk of the implementation-specific functionality into a set of "interpreter" classes. * Renamed LuaSandboxEngine to Scribunto_LuaSandboxEngine * Don't create an engine object unconditionally when the ParserLimitReport hook is called. * Implemented isolation of module global variable namespaces. This means that separate {{#invoke}} calls can't pass data to each other -- this was a desired feature in planning since it allows more flexibility in wikitext parser design. Isolation for mw.import() means that modules cannot accidentally create global variables which affect other modules -- exports are solely via the return value. Change-Id: I3fa35651fe5b1fbfd85adeadc220b1ea31cd6f0b
2012-04-13 10:38:12 +00:00
other than libc. This makes the binaries work on a far greater variety of Linux
distributions.
The following copyright and license restrictions apply to these Lua binaries:
Copyright © 2005-2011 Tecgraf/PUC-Rio and the Kepler Project.
Add comments and remove trailing whitespace Clean up trailing whitespace from all of our code, and add comments indicating that apparently unused variables are ScopedCallbacks. Change-Id: I8e5997797cc7b1c64c5351ec112a18f30edc8fef
2014-07-07 18:46:59 +00:00
Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is furnished to do
Introduced standalone interpreter, implemented module isolation * Introduced a Lua implementation based on shelling out to a standard Lua binary. * Bundled several Lua binaries for common platforms. I haven't added a 32-bit Linux binary yet, but that will come. * Refactored the existing Lua class, bringing out functionality common to all Lua implementations into a set of common base classes. * Moved the bulk of the implementation-specific functionality into a set of "interpreter" classes. * Renamed LuaSandboxEngine to Scribunto_LuaSandboxEngine * Don't create an engine object unconditionally when the ParserLimitReport hook is called. * Implemented isolation of module global variable namespaces. This means that separate {{#invoke}} calls can't pass data to each other -- this was a desired feature in planning since it allows more flexibility in wikitext parser design. Isolation for mw.import() means that modules cannot accidentally create global variables which affect other modules -- exports are solely via the return value. Change-Id: I3fa35651fe5b1fbfd85adeadc220b1ea31cd6f0b
2012-04-13 10:38:12 +00:00
so, subject to the following conditions:
Add comments and remove trailing whitespace Clean up trailing whitespace from all of our code, and add comments indicating that apparently unused variables are ScopedCallbacks. Change-Id: I8e5997797cc7b1c64c5351ec112a18f30edc8fef
2014-07-07 18:46:59 +00:00
The above copyright notice and this permission notice shall be included in all
Introduced standalone interpreter, implemented module isolation * Introduced a Lua implementation based on shelling out to a standard Lua binary. * Bundled several Lua binaries for common platforms. I haven't added a 32-bit Linux binary yet, but that will come. * Refactored the existing Lua class, bringing out functionality common to all Lua implementations into a set of common base classes. * Moved the bulk of the implementation-specific functionality into a set of "interpreter" classes. * Renamed LuaSandboxEngine to Scribunto_LuaSandboxEngine * Don't create an engine object unconditionally when the ParserLimitReport hook is called. * Implemented isolation of module global variable namespaces. This means that separate {{#invoke}} calls can't pass data to each other -- this was a desired feature in planning since it allows more flexibility in wikitext parser design. Isolation for mw.import() means that modules cannot accidentally create global variables which affect other modules -- exports are solely via the return value. Change-Id: I3fa35651fe5b1fbfd85adeadc220b1ea31cd6f0b
2012-04-13 10:38:12 +00:00
copies or substantial portions of the Software.
Add comments and remove trailing whitespace Clean up trailing whitespace from all of our code, and add comments indicating that apparently unused variables are ScopedCallbacks. Change-Id: I8e5997797cc7b1c64c5351ec112a18f30edc8fef
2014-07-07 18:46:59 +00:00
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
Introduced standalone interpreter, implemented module isolation * Introduced a Lua implementation based on shelling out to a standard Lua binary. * Bundled several Lua binaries for common platforms. I haven't added a 32-bit Linux binary yet, but that will come. * Refactored the existing Lua class, bringing out functionality common to all Lua implementations into a set of common base classes. * Moved the bulk of the implementation-specific functionality into a set of "interpreter" classes. * Renamed LuaSandboxEngine to Scribunto_LuaSandboxEngine * Don't create an engine object unconditionally when the ParserLimitReport hook is called. * Implemented isolation of module global variable namespaces. This means that separate {{#invoke}} calls can't pass data to each other -- this was a desired feature in planning since it allows more flexibility in wikitext parser design. Isolation for mw.import() means that modules cannot accidentally create global variables which affect other modules -- exports are solely via the return value. Change-Id: I3fa35651fe5b1fbfd85adeadc220b1ea31cd6f0b
2012-04-13 10:38:12 +00:00
SOFTWARE.
Reference in a new issue Copy permalink