On Sep 9, 2014, at 1:03 PM, Ted Byers <r.ted.by...@gmail.com> wrote: >> El 09/09/2014 20:39, "Larry Bugbee" <bug...@seanet.com> escribió: >>> >>> In the FWIW column.... >>> >>> Please don't mangle names by forcing C++ namespaces. Some us call OpenSSL >>> from Python (and other dynamic languages) and depend on the C naming >>> convention. Adding a "OSSL_" prefix is fine; mangling creates huge >>> problems. >>> > I use a number of such languages and it isn't all that hard to mix > them with C++ (in sme cases, I'd extend them using C++ code, for the > sake of performance). In the case of Python, for example, there is a > boost library designed specifically for that purpose. From my > perspective, that is not a big problem. Rather, it is just one of > countless things I routinely have to deal with: just the cost of > getting things done.
Hi Ted, I would probably agree if I were building production systems. But because I build mostly prototypes, quick usually trumps having to deal with the complexity of C++. OpenSSL and LibTom get used a lot because they are C and super easy to call. When I want classes I build them in Python and call the appropriate OpenSSL functions. Life is much, much simpler when I can stick with Python, C, and Python's ctypes. Then again, if I were building a production app.... My best, Larry > Cheers > > Ted > > -- > R.E.(Ted) Byers, Ph.D.,Ed.D. > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-users@openssl.org > Automated List Manager majord...@openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
