From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f194.google.com (mail-lj1-f194.google.com [209.85.208.194]) (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 E6946445320 for ; Mon, 6 Jul 2020 00:37:26 +0300 (MSK) Received: by mail-lj1-f194.google.com with SMTP id t25so38483941lji.12 for ; Sun, 05 Jul 2020 14:37:26 -0700 (PDT) Date: Mon, 6 Jul 2020 00:37:22 +0300 From: Cyrill Gorcunov Message-ID: <20200705213722.GL2256@grain> References: <20200703144526.522358-1-gorcunov@gmail.com> <20200704073038.GK2256@grain> <0d0901d65311$f8c7a030$ea56e090$@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0d0901d65311$f8c7a030$ea56e090$@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH 00/22] Use void type in empty arguments list List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Timur Safin Cc: 'tml' , 'Vladislav Shpilevoy' , 'Alexander Turenko' On Mon, Jul 06, 2020 at 12:19:30AM +0300, Timur Safin wrote: > : > : > > : > Talking of the patch - why did you change .cc files? AFAIK, in C++ > : > (void) and () are the same. Just no arguments. > : > : True, still we've a mess between () and (void) in cc files, so > : I unified the approach. > > FWIW it's considered bad style to use (void) in C++ instead of () > > https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#nl25-dont-use-void-as-an-argument-type > IIRC we've been planning to switch to C eventually.