The last Lua data type to serialize—threads.
It's more difficult than serializing a function,
but probably a bit easier than serializing a userdata.
I haven't actually tried it yet,
as it can't be done through Lua.
The issue is that there's no API to manipulate the callstack,
and without that,
you're stuck with dipping into the internals of Lua via C,
which explains why most existing serialization modules haven't bothered with threads.
And the only one that has attempted it,
only works for Lua 5.1.
And that's why I didn't bother with it, either.
It was an interesting experience to write a serialization library for Lua.
It became apparent exactly why so many don't bother with functions,
userdata or threads—they're not easy to universally support.
I also skipped out on supporting metatables,
not because they're hard,
but because I just didn't get around to it.
I also think that CBOR makes for a good serialization format.
The primitives are well chosen,
it's a consistent format and the semantic tagging makes it easy to extend.
And like I said earlier,
I had fun playing around with this stuff.
You have my permission to link freely to any entry here. Go
ahead, I won't bite. I promise.
The dates are the permanent links to that day's entries (or
entry, if there is only one entry). The titles are the permanent
links to that entry only. The format for the links are
simple: Start with the base link for this site: http://boston.conman.org/, then add the date you are
interested in, say 2000/08/01,
so that would make the final URL:
You can also specify the entire month by leaving off the day
portion. You can even select an arbitrary portion of time.
You may also note subtle shading of the links and that's
intentional: the “closer” the link is (relative to the
page) the “brighter” it appears. It's an experiment in
using color shading to denote the distance a link is from here. If
you don't notice it, don't worry; it's not all that
It is assumed that every brand name, slogan, corporate name,
symbol, design element, et cetera mentioned in these pages is a
protected and/or trademarked entity, the sole property of its
owner(s), and acknowledgement of this status is implied.