From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp40.i.mail.ru (smtp40.i.mail.ru [94.100.177.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 96F41446441 for ; Sun, 11 Oct 2020 15:57:40 +0300 (MSK) From: Alexander Turenko Date: Sun, 11 Oct 2020 15:57:41 +0300 Message-Id: In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [Tarantool-patches] [PATCH v2 08/15] module api/lua: add API_EXPORT to tuple functions List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladislav Shpilevoy Cc: tarantool-patches@dev.tarantool.org, Alexander Turenko The reason is unification of declarations. It is the rule of thumb to use API_EXPORT with module API functions. Part of #5273 --- src/box/lua/tuple.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/box/lua/tuple.h b/src/box/lua/tuple.h index 0c7e8a16f..fdaf0f8fd 100644 --- a/src/box/lua/tuple.h +++ b/src/box/lua/tuple.h @@ -57,7 +57,7 @@ typedef struct tuple_format box_tuple_format_t; * @retval non-NULL argument is tuple * @throws error if the argument is not a tuple. */ -box_tuple_t * +API_EXPORT box_tuple_t * luaT_checktuple(struct lua_State *L, int idx); /** @@ -66,7 +66,7 @@ luaT_checktuple(struct lua_State *L, int idx); * @sa luaT_istuple * @throws on OOM */ -void +API_EXPORT void luaT_pushtuple(struct lua_State *L, box_tuple_t *tuple); /** @@ -77,7 +77,7 @@ luaT_pushtuple(struct lua_State *L, box_tuple_t *tuple); * @retval non-NULL argument is tuple * @retval NULL argument is not tuple */ -box_tuple_t * +API_EXPORT box_tuple_t * luaT_istuple(struct lua_State *L, int idx); /** -- 2.25.0