[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Suggestion, Lua Sizes
- From: Jay Carlson <nop@<a href="/cgi-bin/echo.cgi?nop.com">...</a>>
- Date: Thu, 16 Feb 2012 17:30:54 -0500
On Mon, Feb 13, 2012 at 5:25 AM, steve donovan
> Most of us have toolboxes of convenient functions, and
> they get used in any non-trivial project. Like functions to split
> strings into tables. I still do this because I don't want to burden
> every one of my public projects with Penlight.
> An interesting possibility is 'static linking' of Lua programs; tools
> like Squish point the way here.
Squish was too complex for me. See and/or seize
http://place.org/~nop/soar-0.0.tar.gz which does static/dynamic
dependency analysis, and creates the expected chunk form:
local function _main()
<body of script goes here>
<body of ml>
...except with more junk around it for various good and not so good
reasons (setenv UNSOAR to get the original script back on stdout etc.)
I blame pl/init.lua for the dynamic analysis, but it does seem to get
penlight apps right if you can hit all the code paths.
Between soar and Squish, "I want to ship a single .lua file" is no
longer a reason to be cut&pasting code into your apps.
>  http://matthewwild.co.uk/projects/squish/home