On Tue, May 3, 2011 at 8:28 PM, Hisham <[email protected]> wrote: > model/inspiration. The major problem is that LR was never designed to > do that, so it uses some globals (local to each module, such as > configuration in luarocks.cfg the table of loaded manifests in > luarocks.manif_core). The API might need to create a context/state > object so that multiple instances could exist independently in an > application.
Yes that would be ideal, although I can't think off-hand of any use cases that would require it. I like thinking in code, while doing the necessary abstract thinking as a background task. So I would kick off by providing a Rock which would implement some specific functionality, say that of 'luarocks show'. This module would be luarocks.api.show. In parallel, people can think of what a useful and flexible LuaRocks API could look like. At the end of the process, there could be some LR refactoring to use the API internally, but it's useful to have something concrete to play with first. steve d. _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
