1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
|
luaposix
========
By the [luaposix project][GitHub]
[](http://travis-ci.org/luaposix/luaposix/builds)
luaposix is a POSIX binding, including curses, for [Lua] 5.1 and 5.2;
like most libraries it simply binds to C APIs on the underlying
system, so it won't work on non-POSIX systems. However, it does try
to detect the level of POSIX conformance of the underlying system and
bind only available APIs.
luaposix is released under the MIT license, like Lua (see [COPYING];
it's basically the same as the BSD license). There is no warranty.
Please report bugs and make suggestions by opening an issue on the
github tracker.
Installation
------------
The simplest way to install luaposix is with [LuaRocks]. To install the
latest release (recommended):
luarocks install luaposix
To install current git master (for testing):
luarocks install https://raw.github.com/luaposix/luaposix/release/luaposix-git-1.rockspec
With Lua 5.1, luaposix requires the bitop library from http://bitop.luajit.org/
(On Lua 5.2 it will work whether bitop is installed or not.)
To install without LuaRocks, check out the sources from the
[repository][GitHub] and run the following commands:
cd luaposix
./bootstrap
./configure --prefix=INSTALLATION-ROOT-DIRECTORY
make all check install
Dependencies are listed in the dependencies entry of the file
`rockspec.conf`. You will also need Autoconf and Automake.
See [INSTALL] for `configure` instructions and `configure --help`
for details of available command-line switches.
Use
---
The library is split into two modules. The basic POSIX APIs are in
`posix` and the curses APIs in `curses`.
HTML documentation can be generated with [LDoc] by running `make doc`
or viewed online at <http://luaposix.github.com/luaposix/>.
The authoritative online POSIX reference is at
<http://www.opengroup.org/onlinepubs/007904875/toc.htm>.
Example code
------------
See the example program `tree.lua`, along with the tests in
`tests-*.lua`.
For a complete application, see the lua branch of [GNU Zile].
Bugs reports & patches
----------------------
Bug reports and patches are most welcome. Please use the github issue
tracker (see URL at top). There is no strict coding style, but please
bear in mind the following points when writing new code:
0. Follow existing code. There are a lot of useful patterns and
avoided traps there.
1. 8-character indentation using TABs. Not my favourite either, but
better than reformatting the code and losing much of the ability to
follow the version control history.
2. No non-POSIX APIs; no platform-specific code. When wrapping APIs
introduced in POSIX 2001 or later, add an appropriate #if. If your
platform isn't quite POSIX, you may find a gnulib module to bridge
the gap. If absolutely necessary, use autoconf feature tests.
3. Thin wrappers: although some existing code contradicts this, wrap
POSIX APIs in the simplest way possible. If necessary, more
convenient wrappers can be added in Lua (posix.lua).
[Lua]: http://www.lua.org/
[GitHub]: https://github.com/luaposix/luaposix
[LuaRocks]: http://www.luarocksporg "Lua package manager"
[LDoc]: https://github.com/stevedonovan/LDoc "Lua documentation generator"
[COPYING]: https://raw.github.com/luaposix/luaposix/release/COPYING
[INSTALL]: https://raw.github.com/luaposix/luaposix/release/INSTALL
[GNU Zile]: http://git.savannah.gnu.org/cgit/zile.git/log/?h=lua "A cut-down Emacs clone"
|
