Browse Source

readme: Do not keep track of test results on a development branch

Ole 11 years ago
parent
commit
a6be8d4b43
1 changed files with 0 additions and 8 deletions
  1. 0 8
      README.md

+ 0 - 8
README.md

@@ -23,14 +23,6 @@ Assuming all headers are located in `/usr/include/lua5.3` and the shared object
 make LUA_INCDIR=/usr/include/lua5.3 LUA_LIBNAME=lua5.3 test
 make LUA_INCDIR=/usr/include/lua5.3 LUA_LIBNAME=lua5.3 test
 ```
 ```
 
 
-Results on recent versions of Arch Linux and FreeBSD:
-
- Compiler    | Lua 5.1<sup>*</sup> | Lua 5.2<sup>*</sup> | Lua 5.3
--------------|---------------------|---------------------|---------
- clang++ 3.5 | partial             | partial             | passes
- clang++ 3.6 | partial             | partial             | passes
- g++ 5.1     | partial             | partial             | passes
-
 <sup>*</sup> Assertions relying on `lua_Integer` will fail, due to integer quirks in Lua. This
 <sup>*</sup> Assertions relying on `lua_Integer` will fail, due to integer quirks in Lua. This
 should only concern you if your application expects Lua integers to work like normal integers,
 should only concern you if your application expects Lua integers to work like normal integers,
 because they don't.
 because they don't.