On Fri, Oct 18, 2013 at 08:16:32AM +0100, Alexander Nasonov wrote: > First of all, the code has been imported the wrong way as I stated in > the previous email. You should properly import Lua 5.2 to sys/external/ > and then apply local changes required to run it in kernel space.
I agree. Already for the sake of consistency and sanity; if one looks at at sys/modules, there is no existing code in it. On Fri, Oct 18, 2013 at 09:29:44AM +0200, Marc Balmer wrote: > This was not an import of Lua. The Lua sources already are in the tree. > When we are ready to move from Lua 5.1 to Lua 5.2, Lua 5.2 will be > imported to sys/external, as I already mentioned. Why not do things right the first time? Sounds a like a recipe for a mess. - Jukka.