Human-readable representation of Lua tables
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
inspect.lua/README.textile

128 lines
2.7 KiB

14 years ago
h1. inspect.lua
This function transform any Lua table into a human-readable representation of that table.
The objective here is human understanding (i.e. for debugging), not serialization or compactness.
h1. Examples of use
14 years ago
"Array-like" tables are rendered horizontally:
<pre>inspect({1,2,3,4}) == "{ 1, 2, 3, 4 }"</pre>
"dictionary-like" tables are rendered with one element per line:
<pre>inspect({a=1,b=2}) == [[{
a = 1,
b = 2
}]]</pre>
The keys will be sorted alphanumerically when possible.
"Hybrid" tables will have the array part on the first line, and the dictionary part just below them:
<pre>
inspect({1,2,3,a=1,b=2}) == [[{ 1, 2, 3,
a = 1,
b = 2
}]]
</pre>
Tables can be nested, and will be indented with two spaces per level.
<pre>
inspect({a={b=2}}) = [
a = {
b = 2
}
}]]
</pre>
By default, @inspect@ will stop rendering at a depth of 4 levels. When that point is reached, it will just return @{...}@ :
<pre>
local t5 = {a = {b = {c = {d = {e = 5}}}}}
inspect(t5) == [[
a = {
b = {
c = {
d = {...}
}
}
}
}]]
</pre>
You can increase/decrease the max depth with the second parameter:
<pre>
inspect(t5, 2) == [[{
a = {
b = {...}
}
}]])
inspect(t5, 7) == [[{
a = {
b = {
c = {
d = {
e = 5
}
}
}
}
}]])
</pre>
Functions, userdata and threads are simply rendered as @<function>@, @<userdata>@ and @<thread>@ respectively:
<pre>
inspect({ f = print, ud = some_user_data, thread = a_thread} ) == [[{
f = <function>,
u = <userdata>,
thread = <thread>
}]])
</pre>
If the table has a metatable, inspect will include it at the end, in a special field called @<metatable>@:
<pre>
inspect(setmetatable({a=1}, {b=2}) == [[{
a = 1
<metatable> = {
b = 2
}
}]])
</pre>
14 years ago
h1. Gotchas / Warnings
14 years ago
This method is *not* appropiate for saving/restoring tables. It is ment to be used by the programmer mainly while debugging a program.
14 years ago
h1. Installation
Just copy the inspect.lua file somewhere in your projects (maybe inside a /lib/ folder) and require it accordingly.
Remember to store the value returned by require somewhere! (I suggest a local variable named inspect, altough others might like table.inspect)
<pre>
local inspect = require 'inspect'
-- or --
table.inspect = require 'inspect'
</pre>
Also, make sure to read the license file; the text of that license file must appear somewhere in your projects' files.
h1. Specs
This project uses "telescope":https://github.com/norman/telescope for its specs. If you want to run the specs, you will have to install telescope first. Then just enter the spec folder and execute run.lua:
<pre>
cd path/to/inspect.lua/specs
lua run.lua
</pre>