From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WEJIP-00038W-1w for ltp-list@lists.sourceforge.net; Fri, 14 Feb 2014 13:59:13 +0000 Received: from userp1040.oracle.com ([156.151.31.81]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WEJIN-0000GJ-2m for ltp-list@lists.sourceforge.net; Fri, 14 Feb 2014 13:59:12 +0000 Message-ID: <52FE2132.5060601@oracle.com> Date: Fri, 14 Feb 2014 17:59:14 +0400 From: Alexey Kodanev MIME-Version: 1.0 References: <1392112090-13853-1-git-send-email-alexey.kodanev@oracle.com> <5757763.zAWEHsmlGc@vapier> <52FC98EC.80406@oracle.com> <2020103.1jVMlSvdbW@vapier> In-Reply-To: <2020103.1jVMlSvdbW@vapier> Subject: Re: [LTP] [PATCH 4/4] lib: add tst_res_r.c List-Id: Linux Test Project General Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ltp-list-bounces@lists.sourceforge.net To: Mike Frysinger Cc: vasily.isaenko@oracle.com, ltp-list@lists.sourceforge.net Hi! On 02/14/2014 03:06 AM, Mike Frysinger wrote: > On Thursday, February 13, 2014 14:05:32 Alexey Kodanev wrote: >> On 02/13/2014 12:47 PM, Mike Frysinger wrote: >>> On Tuesday, February 11, 2014 13:48:10 Alexey Kodanev wrote: >>>> +static int get_tst_count() >>> random note: never never never use () with functions. always always >>> always >>> use (void). i'm guessing you're not aware, but what you've written here >>> may> >>> be called (warning free!) like so: >>> get_tst_count(1, 2, 3); >>> >>> yes, even with -W -Wall -Wextra. please stamp this horrible habit out of >>> your code. >> Thank you for explanation! >> There is a trick to try g++ to compile the code, it will throw an error >> on that and stops compilation. > yeah, C++ fixed this historical wart of C. sorry for not clarifying. > > iiuc (and i could be wrong as i'm not old enough to have lived through it), > this dates back to when C (ANSI?) didn't have prototypes. with a lot of code > out there relying on the behavior, gcc never stopped accepting it. > > i wonder if we could argue for like a newer GNU standard to reject it. > -mike True, what about -Wold-style-definition option? It will reveal old-style usage, at least would print a warning... Compiled LTP with the option, got 2 thousand warnings! There are truly a lot of code which is still using it and LTP's code one of them. Best regards, Alexey ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list