lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <f7cbb08dded668f07401276266689933f31dd23d.camel@perches.com>
Date:   Sat, 12 May 2018 09:24:41 -0700
From:   Joe Perches <joe@...ches.com>
To:     "igor.stoppa@...il.com" <igor.stoppa@...il.com>
Cc:     Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org
Subject: Re: [RFC: Coding Style] Best way to split a long function
 declaration with modifiers

On Sat, 2018-05-12 at 19:07 +0300, igor.stoppa@...il.com wrote:
> On 12 May 2018 at 18:41, Joe Perches <joe@...ches.com> wrote:
> 
> > 
> > I think the first style should be preferred when the
> > combined character length of <type> <function_name> is
> > relatively long.
> > 
> 
> thank you, I could provide a patch to the docs for this case, if it's not
> considered too much of a corner case.

I think it should not considered anything like a mandate.

Perhaps it could be described as an optional/possible style
but perhaps as well it's not necessary as coding_style for
this does not have to be rigidly specified.

cheers, Joe

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ