> From: owner-openssl-us...@openssl.org [mailto:owner-openssl- > us...@openssl.org] On Behalf Of Iñaki Baz Castillo > Sent: Monday, 08 September, 2014 18:14 > To: openssl-users@openssl.org > Subject: Re: Why does OpenSSL own all the prefixes in the world? > > 2014-09-08 16:29 GMT+02:00 Salz, Rich <rs...@akamai.com>: > > The extern "C" makes it difficult to put things into a namespace. You'd > either have to write class declarations that used NO public openssl header > files in their public declaration, or we'd have to change the extern "C" > wrappers to be something like > > #if defined(__cplusplus) && !defined(OPENSSL_NAMESPACED_API) > > > I've tried the "namespace openssl { #include <openssl/xxxx.h> } > approach and it has been terrible. I've ended with compiler error > messages like: > > openssl::malloc not found > > It makes sense given that the namespace is also affecting to any other > include within the openssl header file.
You'd have to include the standard C headers before including the OpenSSL ones, outside the namespace, so that their inclusion by the OpenSSL headers has no effect. Mind you, I don't think it's worth the effort, for the reasons I outlined earlier. -- Michael Wojcik Technology Specialist, Micro Focus This message has been scanned for malware by Websense. www.websense.com
