From: "Timur Safin" <tsafin@tarantool.org> To: 'Igor Munkin' <imun@tarantool.org>, 'Vladislav Shpilevoy' <v.shpilevoy@tarantool.org> Cc: tarantool-patches@dev.tarantool.org, 'Alexander Turenko' <alexander.turenko@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH 2.X 4/7] module api: luaL_register_module & luaL_register_type Date: Fri, 2 Oct 2020 19:14:19 +0300 [thread overview] Message-ID: <0ada01d698d7$15b21030$41163090$@tarantool.org> (raw) In-Reply-To: <20200929080304.GV18920@tarantool.org> : From: Igor Munkin <imun@tarantool.org> : Subject: Re: [Tarantool-patches] [PATCH 2.X 4/7] module api: : luaL_register_module & luaL_register_type : : Vlad, : : I glanced the patch and doubt these functions need to be exported by : Tarantool. These functions neither wrap internals nor provide any : performance benefits (e.g. reduce numbers of excess allocations). It : would be nice to have such auxiliary interfaces in so called "modulekit" : to make third party modules development easier, but I see no problem to : borrow this code to merger/key_def as is for now. Ok, let me put it another way: - we are agreed that this is necessary useful functionality which might be part of some static library, as part of modulekit? - we are not ok to put those symbols to Tarantool, and use Tarantool executable(s) for linking against those symbols, because it's looking too much intimate. - I'd hardly imagine situation that for such modulekit code reuse we would prefer to introduce yet another repository, compile it as static library and then add to the linking dependencies of an external module? (or do we?) - as for me it's still looking part of module api (some headers, and some Helpers in library), and I'd prefer to simply export them from executable... But.. if we prefer "modulekit" then yes, I'd copy-paste this code to my module and to the GitHub template for Tarantool c modules (yet to be created). Looks redundant, but will save a couple of external symbols. Regards, Timur : : On 29.09.20, Vladislav Shpilevoy wrote: : > Thanks for the patch! : > : > See 2 comments below. : > : > On 24.09.2020 19:00, Timur Safin wrote: : > > Exporting `luaL_register_module` & `luaL_register_type` : > > functions as they needed for external merger : > > : > > diff --git a/src/lua/utils.h b/src/lua/utils.h : > > index 7639cd64a..9b1fe7e57 100644 : > > --- a/src/lua/utils.h : > > +++ b/src/lua/utils.h : > > @@ -78,6 +78,8 @@ luaL_pushuuid(struct lua_State *L); : > > : > > /** \cond public */ : > > : > > +struct luaL_Reg; : > : > 1. It does not seem to be public. How are users supposed to work with : that? : > Igor, could you please take a look at this? : : It's public[1] and is provided by <lauxlib.h> Lua standard header as : Sasha already mentioned it in the thread. : : > : : <snipped> : : [1]: https://www.lua.org/manual/5.1/manual.html#luaL_Reg : : -- : Best regards, : IM
next prev parent reply other threads:[~2020-10-02 16:14 UTC|newest] Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-24 17:00 [Tarantool-patches] [PATCH 2.X 0/7] RFC: module api: extend for external merger Lua module Timur Safin 2020-09-24 17:00 ` [Tarantool-patches] [PATCH 2.X 1/7] module api: export box_tuple_validate Timur Safin 2020-09-28 22:20 ` Vladislav Shpilevoy 2020-10-02 12:24 ` Timur Safin 2020-10-09 1:11 ` Alexander Turenko 2020-10-09 20:11 ` Vladislav Shpilevoy 2020-10-10 1:19 ` Alexander Turenko 2020-09-29 5:25 ` Alexander Turenko 2020-10-05 7:35 ` Alexander Turenko 2020-09-24 17:00 ` [Tarantool-patches] [PATCH 2.X 2/7] module api: export box_key_def_dup Timur Safin 2020-09-28 22:21 ` Vladislav Shpilevoy 2020-09-29 5:03 ` Alexander Turenko 2020-09-29 23:19 ` Vladislav Shpilevoy 2020-10-01 3:05 ` Alexander Turenko 2020-10-02 12:25 ` Timur Safin 2020-10-02 12:26 ` Timur Safin 2020-09-24 17:00 ` [Tarantool-patches] [PATCH 2.X 3/7] module api: luaT_newthread Timur Safin 2020-09-28 22:21 ` Vladislav Shpilevoy 2020-10-02 12:27 ` Timur Safin 2020-10-02 21:48 ` Vladislav Shpilevoy 2020-09-29 6:25 ` Alexander Turenko 2020-10-02 12:26 ` Timur Safin 2020-10-02 12:53 ` Alexander Turenko 2020-09-29 15:19 ` Igor Munkin 2020-10-02 16:12 ` Timur Safin 2020-10-03 16:57 ` Igor Munkin 2020-09-24 17:00 ` [Tarantool-patches] [PATCH 2.X 4/7] module api: luaL_register_module & luaL_register_type Timur Safin 2020-09-28 22:21 ` Vladislav Shpilevoy 2020-09-29 5:09 ` Alexander Turenko 2020-09-29 23:20 ` Vladislav Shpilevoy 2020-09-30 6:31 ` Alexander Turenko 2020-09-30 6:33 ` Alexander Turenko 2020-10-02 16:14 ` Timur Safin 2020-09-29 8:03 ` Igor Munkin 2020-09-29 23:21 ` Vladislav Shpilevoy 2020-10-02 16:14 ` Timur Safin [this message] 2020-10-03 3:24 ` Alexander Turenko 2020-09-24 17:00 ` [Tarantool-patches] [PATCH 2.X 5/7] module api: luaT_temp_luastate & luaT_release_temp_luastate Timur Safin 2020-09-28 22:21 ` Vladislav Shpilevoy 2020-09-29 5:17 ` Alexander Turenko 2020-09-29 23:21 ` Vladislav Shpilevoy 2020-10-01 3:35 ` Alexander Turenko 2020-09-29 15:10 ` Igor Munkin 2020-09-29 21:03 ` Alexander Turenko 2020-09-29 23:23 ` Vladislav Shpilevoy 2020-09-30 10:09 ` Alexander Turenko 2020-10-01 15:06 ` Igor Munkin 2020-10-03 2:16 ` Alexander Turenko 2020-10-02 12:24 ` Timur Safin 2020-09-24 17:00 ` [Tarantool-patches] [PATCH 2.X 6/7] module api: luaL_checkibuf & luaL_checkconstchar Timur Safin 2020-09-28 22:21 ` Vladislav Shpilevoy 2020-09-29 5:53 ` Alexander Turenko 2020-09-29 23:25 ` Vladislav Shpilevoy 2020-10-01 3:00 ` Alexander Turenko 2020-10-02 16:14 ` Timur Safin 2020-10-02 21:48 ` Vladislav Shpilevoy 2020-10-08 13:50 ` Timur Safin 2020-09-24 17:00 ` [Tarantool-patches] [PATCH 2.X 7/7] module api: luaL_cdata_iscallable Timur Safin 2020-09-28 22:21 ` Vladislav Shpilevoy 2020-09-29 5:19 ` Alexander Turenko 2020-10-02 16:14 ` Timur Safin 2020-10-02 12:23 ` [Tarantool-patches] [PATCH 2.X 0/7] RFC: module api: extend for external merger Lua module Timur Safin 2020-10-02 21:49 ` Vladislav Shpilevoy 2020-10-03 2:54 ` Alexander Turenko
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='0ada01d698d7$15b21030$41163090$@tarantool.org' \ --to=tsafin@tarantool.org \ --cc=alexander.turenko@tarantool.org \ --cc=imun@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 2.X 4/7] module api: luaL_register_module & luaL_register_type' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox