From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f193.google.com (mail-lj1-f193.google.com [209.85.208.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 9282F4696C3 for ; Mon, 13 Apr 2020 21:17:25 +0300 (MSK) Received: by mail-lj1-f193.google.com with SMTP id u15so5181496ljd.3 for ; Mon, 13 Apr 2020 11:17:25 -0700 (PDT) Date: Mon, 13 Apr 2020 21:17:22 +0300 From: Cyrill Gorcunov Message-ID: <20200413181722.GY3072@uranus> References: <20200413164435.GX3072@uranus> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Tarantool-patches] [PATCH 00/43] Unhide symbols List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladislav Shpilevoy Cc: tarantool-patches@dev.tarantool.org On Mon, Apr 13, 2020 at 07:57:36PM +0200, Vladislav Shpilevoy wrote: > > > > Vladislav, let me summarize the overall idea and the problem: > > > > 1) Currently tarantool *already* uses extra/exports file during > > build procedure, where we keep the list of functions to be > > avaliable via Lua ffi interface to the tarantool users. > > > > While these functions are NOT part of API people relay on them > > and use actively, right? In other words they are semi-API I wold > > say. > > Almost correct. Many symbols here are a part of the public API. > But some of them are not, and yet it does not mean people use them, > at least directly. > > Non-public symbols are used by Lua FFI, by our own Lua code. So > the exported but non-public symbols we can change as we want. > Even remove from the export list when they become not needed. > > Everything else is correct. Ok, as to me this approach a way better than current extra/export idiocity. I can't step in with you and Kostya since I've too little experience over all architecture, thus up to you guys! As to code itself -- Ack.