>Philip Guenther <guent...@gmail.com> writes: > >> There are four options here: >> 1) change the software to not use the name 'bcrypt' for a non-static >> function. OpenBSD has only been using it for 15 years... > >Agree, but for now I'm trying to keep changes to a minimum as I work out >larger issues. This is in an erlang wrapper for bcrypt. It includes its >own copy of bcrypt.c > >The change that diverges from the OpenBSD version is in this commit, in >case anyone is interested. > >https://github.com/smarkets/erlang-bcrypt/commit/1277ee41bba86d47e039e3f24a47a491efe48d78
Whoever did that should have renamed it. There really is no excuse. I look forward to the amusing consequences in the future.
