From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id BB7E626115 for ; Wed, 31 Jul 2019 12:58:35 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iqq5Yn_A_UAu for ; Wed, 31 Jul 2019 12:58:35 -0400 (EDT) Received: from smtp31.i.mail.ru (smtp31.i.mail.ru [94.100.177.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id 7CF81260A4 for ; Wed, 31 Jul 2019 12:58:35 -0400 (EDT) Subject: [tarantool-patches] Re: [PATCH v2 1/2] lua: new function luaT_return_error() References: <20190731152324.4rraz2shvqnenaas@tkn_work_nb> <5abcd784-f790-5675-fae0-1620e264a221@tarantool.org> <4927f71a-2141-4412-6298-0c48b28b25ec@tarantool.org> From: Vladislav Shpilevoy Message-ID: Date: Wed, 31 Jul 2019 19:00:44 +0200 MIME-Version: 1.0 In-Reply-To: <4927f71a-2141-4412-6298-0c48b28b25ec@tarantool.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: tarantool-patches-bounce@freelists.org Errors-to: tarantool-patches-bounce@freelists.org Reply-To: tarantool-patches@freelists.org List-Help: List-Unsubscribe: List-software: Ecartis version 1.0.0 List-Id: tarantool-patches List-Subscribe: List-Owner: List-post: List-Archive: To: Imeev Mergen , tarantool-patches@freelists.org, Alexander Turenko Cc: kostja@tarantool.org On 31/07/2019 18:20, Imeev Mergen wrote: > > On 7/31/19 6:40 PM, Vladislav Shpilevoy wrote: >> >> On 31/07/2019 17:23, Alexander Turenko wrote: >>>> +/** >>>> + * Return nil as the first return value and an error as the >>>> + * second. The error is received using box_error_last(). >>>> + * >>>> + * @param L Lua stack. >>>> + */ >>>> +LUA_API int >>>> +luaT_return_error(lua_State *L); >>> Maybe let the name be a bit more explicit, say, >>> luaT_push_conventional_error(struct lua_State *L)? >>> >> Please, no. You work too much with Java. The name >> is too long. Maybe luaT_push_nil_err()? > I thought that luaT_error() throws an error, and this one returns > it. So I called it luaT_return_error(). Should I change the name > to luaT_push_nil_err()? > For me 'return' was ok, but seems it is not ok for Kostja and Alexander. Lets wait.