➢ In general we should prefer ossl_assert over assert. Never use
OPENSSL_assert() in libcrypto or libssl.
Maybe that’s all to put into the guide, then.
___
openssl-project mailing list
openssl-project@openssl.org
Am 05.02.2018 um 19:13 schrieb Salz, Rich:
>
>
> Do not put a size after sizeof; do use parens.
>
nit: Do not put a /space /after sizeof.
>
>
> Treat a single-statement with comment as if it were multi-line and use
> curly braces
>
>
>
> if (test()) {
>
>
I filed the annual registration for OpenSSL Software Services and paid with the
OpenSSL credit card.
From: CT Corporation
Reply-To: "[DO NOT REPLY] CT Corporation"
Date: Monday, February 5, 2018 at 1:32 PM
To: "rs...@openssl.org"
A summary of the discussion thread so far. Not surprisingly, it’s all about
the whitespace. :)
The descriptions here were written to be understandable stand-alone. Once we
come to a conclusion, we’ll wordsmith them into the coding style.
Do not put a size after sizeof; do use parens.
When
On Mon, Feb 05, 2018 at 08:43:04PM +0100, Dr. Matthias St. Pierre wrote:
>
>
> Am 05.02.2018 um 19:13 schrieb Salz, Rich:
> >
> >
> > Do not put a size after sizeof; do use parens.
> >
>
> nit: Do not put a /space /after sizeof.
>
> >
> >
> > Treat a single-statement with comment as if it
On 05/02/18 19:43, Dr. Matthias St. Pierre wrote:
>
> Wasn't there also the suggestion by someone that if one part of an
> if-else statements needs braces that the other part should get some, too?
That's already in the style guide:
Do not unnecessarily use braces around a single statement:
* nit: Do not put a space after sizeof.
fixed.
* Wasn't there also the suggestion by someone that if one part of an
if-else statements needs braces that the other part should get some, too?
It already says that.
___
openssl-project mailing