From: "Lukas Prochazka" <lpr@pontex.cz>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: lua tables - how do you cope?
Date: Sat, 30 Jul 2016 23:46:07 +0200 [thread overview]
Message-ID: <20160730214607.baa61a4c@mail.pontex.cz> (raw)
In-Reply-To: <6D88EA0A-428E-45E1-88FF-A7BE831AC8D5@uni-bonn.de>
Hello Thomas,
here is my "dump()" I've been using for several years:
----
function dump(arg, opts) -- .seen, .pfx
if type(opts) == "string" then print(opts); opts = nil
elseif opts == true then print("-- (dump)"); opts = nil
end
local pfx = opts and opts.pfx
local seen = opts and opts.seen or {}
if type(arg) == "table" then
if pfx then pfx = pfx .. "]["
else
pfx = "["
--seen = {}
end
seen[arg] = tostring(arg) --true
local keys = {}
do
-- Sort keys, if all are strings
local strs_only = true
for k in pairs(arg) do
if strs_only and type(k) ~= "string" then strs_only = false end
keys[#keys + 1] = k
end
if strs_only then table.sort(keys) end
end
for _, key in ipairs(keys) do
local val = arg[key]
io.write(pfx .. tostring(key) .. "] = " .. tostring(val) .. "\t(" .. type(val) .. ")")
if type(val) == "table" then
if seen[val] then print(" (seen)")
else
print()
dump(val, {pfx = pfx .. tostring(key), seen = seen}) --pfx .. tostring(key), seen)
end
else
print()
end
end
else
print(arg)
end
end
----
Try:
----
a = {c = 1, b = 2}; a.a = a
dump(a)
dump(a, "This is 'a'.")
----
Improvements or parametrization of visualizing style would be possible, of course...
Best regards,
Lukas
----- Original Message -----
From: Schmitz Thomas A. [mailto:thomas.schmitz@uni-bonn.de]
To: mailing list for ConTeXt users [mailto:ntg-context@ntg.nl]
Sent: Sat, 30 Jul 2016 23:01:29 +0100
Subject: Re: [NTG-context] lua tables - how do you cope?
> Thank you, but this is not what I’m looking for. I know how to sort a table, and I know the Lua table tutorial (the Lua wiki is, IMHO, really terrible and disorganized). I have to construct deeply nested tables and sometimes lose track of what is at what level of my table, so I was wondering if there was an easy way of visualizing a nested table. On the web, you can find a number of (mostly abandoned) projects; the one at http://siffiejoe.github.io/lua-microscope/ says: "Many Lua programmers have written their own pretty-printer or data dumper and some even use it for (de-)serializing Lua data structures.” So I was wondering if any of the Lua users here on the list has something they want to share.
Thomas
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-07-30 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 10:20 Schmitz Thomas A.
2016-07-30 13:04 ` Joseph Canedo
2016-07-30 14:31 ` Wolfgang Schuster
2016-07-30 21:01 ` Schmitz Thomas A.
2016-07-30 21:19 ` Arthur Reutenauer
2016-07-30 21:46 ` Lukas Prochazka [this message]
2016-07-30 22:25 ` Schmitz Thomas A.
2016-07-30 22:26 ` Hans Hagen
2016-07-30 22:28 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160730214607.baa61a4c@mail.pontex.cz \
--to=lpr@pontex.cz \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).