sol2/.gitignore

obj/*
bin/*
demacro.txt
Shinobi2
dev*
lua-5.2.2/
Debug/
Release/
x64/
*.vcxproj
*.vcxproj.filters
*.tlog
*.lastbuildstate
*.idb
*.sln
*.gitattributes
liblua.a
sol/include/
.ninja*
include/
lib/liblua5.2.a
*.config
*.creator
*.files
*.includes
*.pyc
main.cpp
lua-5.2.3/
build.ninja
main.ninja
*.user
*.3cb9f6a
luajit-2.0.3/
.dropbox*
desktop.ini
lua-5.3.0/
.vs/
lua-5.1.5/
luajit-2.0.4/
*.creator.user.*
Adding mingw libraries (liblua.a) to gitignore 2013-12-08 10:17:07 +08:00			`obj/*`
			`bin/*`
			`demacro.txt`
			`Shinobi2`
Switch from static member strings to userdata_traits 2014-04-27 17:08:39 +08:00			`dev*`
Adding mingw libraries (liblua.a) to gitignore 2013-12-08 10:17:07 +08:00			`lua-5.2.2/`
			`Debug/`
			`Release/`
			`x64/`
			`*.vcxproj`
			`*.vcxproj.filters`
			`*.tlog`
			`*.lastbuildstate`
			`*.idb`
			`*.sln`
			`*.gitattributes`
			`liblua.a`
Improved tests, added a build.ninja for TeamCity, and fixed formatting again to work with Rapptz's style. 2013-12-12 00:18:13 +08:00			`sol/include/`
			`.ninja*`
Have I mentioned I hate GCC? I hate GCC. 2013-12-12 00:56:34 +08:00			`include/`
Additions for gitignore for the new files that are necessary to kick around qtCreator Fix for userdata to accept base classes where the derived class uses the name of a base member function to access it (Derived::get_num, where get_num is only implemented in Base::get_num) VC++ makes this acceptance easy by taking the name as "Derived", but GCC and Clang 2014-05-26 01:46:23 +08:00			`lib/liblua5.2.a`
			`*.config`
			`*.creator`
			`*.files`
			`*.includes`
Switched over to bootstrap.py script 2014-06-06 06:37:46 +08:00			`*.pyc`
Additions for gitignore for the new files that are necessary to kick around qtCreator Fix for userdata to accept base classes where the derived class uses the name of a base member function to access it (Derived::get_num, where get_num is only implemented in Base::get_num) VC++ makes this acceptance easy by taking the name as "Derived", but GCC and Clang 2014-05-26 01:46:23 +08:00			`main.cpp`
Fix for Issue #35 Userdata now properly forwards arguments to constructor get_call now properly has extra parameters to allow for forwarding items from the first call that are not popped Added tests to cover new cases 2014-06-27 16:25:57 +08:00			`lua-5.2.3/`
			`build.ninja`
			`main.ninja`
Additions to gitignore. 2014-08-09 19:55:35 +08:00			`*.user`
			`*.3cb9f6a`
Additional ignores 2014-12-18 05:12:51 +08:00			`luajit-2.0.3/`
			`.dropbox*`
			`desktop.ini`
This mega-commit introduces Visual Studio 2015 CTP 6 support. sol::object had a few reference leaks in the way it retrieved values: it now does it properly without leaving the stack at +1 item sol::stack was drastically cleaned up, with the following key change: * sol::stack::push now returns an integer of the number of things its pushed (usually 1, but can be more) (Thanks, @PrincessNyanara!) * sol::stack::call now calls functions flexibly, and getting is done more reliably * due to the innovation of stack::call and using absolute indices, we no longer have to use reverse_call style programming to deal with lua * sol::reference::get_type is now const-correct * sol::state and sol::table now have a cleaned up `get` implementation since it is no longer held back by the ugliness of VC++'s incapability to handle templates * the name `sol::userdata` now belongs to a type that actually encapsualtes a void* with a pusher/getter than gets a userdata void* value (TODO: give it a template to make it static_cast to that type on get?) * lightuserdata_t -> light_userdata, upvalue_t -> upvalue as type names (mostly details) * pushers for various types were updated to return integers 2015-03-02 10:14:42 +08:00			`lua-5.3.0/`
Updated copyright headers and added compatibility with lua 5.1.5 and luajit! This means sol can now run on the fastest dynamic language implementation ever! Wooo!~ 2015-05-25 09:29:21 +08:00			`.vs/`
			`lua-5.1.5/`
			`luajit-2.0.4/`
Thanks to LUA_MULTRET, we can have normal function call syntax with `sol::function` that doesn't require the user to pass the arguments in directly with `.call<Return1, Return2, Return3>( ... )` function result is meant to be transient, and therefore should not be regularly storeable by the user... but there is no way to make a "and you can't have anything but a temporary to this" type, as far as I can tell. 2015-07-19 22:26:11 +08:00			`.creator.user.`