API renaming

[Dr Paul Dale]

Adherence to the code style will also be required (indentation will change).  This will be harder to automate.

Changing EVP_RAND -> OSSL_RAND is worse because it will change line breaks as well as indentation.  OSSL_RNG avoids this, if we accept not using RAND in the name.
KDF and MAC also get longer and would have the same issue.


Then there are the inevitable merge conflicts….


Pauli
-- 
Dr Paul Dale | Distinguished Architect | Cryptographic Foundations 
Phone +61 7 3031 7217
Oracle Australia




> On 24 Jul 2020, at 6:15 pm, Dr. Matthias St. Pierre <Matthias.St.Pierre at ncp-e.com> wrote:
> 
>> I was thinking OSSL_LIBCTX?
> 
> That's a good choice and consistent with how we name the variable in most (but not all) places:
> 
> 	OPENSSL_CTX *libctx;
> 
> I volunteer to raise a pull request which does a scripted bulk rename, as soon as we have made
> a decision. Ideally, the bulk renaming should go in shortly before the next alpha. Having it
> automated by a script would ease rebasing of other still unmerged pull requests over the change.
> 
> Matthias
> 
>> -----Original Message-----
>> From: SHANE LONTIS <shane.lontis at oracle.com>
>> Sent: Friday, July 24, 2020 9:43 AM
>> To: Dr. Matthias St. Pierre <Matthias.St.Pierre at ncp-e.com>
>> Cc: Richard Levitte <levitte at openssl.org>; openssl-project at openssl.org
>> Subject: Re: API renaming
>> 
>> I was thinking OSSL_LIBCTX?
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mta.openssl.org/pipermail/openssl-project/attachments/20200724/a0796de6/attachment.html>