On 04/07/2010 10:26 AM, Chad Seibert wrote:

Hi,

I've just got confirmation from Jack Lloyd that I can port Botan to Boost. He only uses Boost.Python currently because he was having issues with shared_ptr when compiling for ARM. However, I think that most of these issues will be resolved (or have been) when the porting process takes place.

What about starting with a little abstract, describing what Botan is, i.e. what functionality it offers, and why that would be a good addition to boost ?

Is there any protocol for porting an entire library to Boost? I know that ASIO took a while for approval.

I'd expect this to follow the same process every other new library used, i.e. start by proposing a library, iterating through discussions and improvements, then submit a formal proposal once you feel confident that the API is complete and stable. Stefan -- ...ich hab' noch einen Koffer in Berlin...

On 07/04/2010 10:26 AM, Chad Seibert wrote:

Hi,

I've just got confirmation from Jack Lloyd that I can port Botan to Boost. He only uses Boost.Python currently because he was having issues with shared_ptr when compiling for ARM. However, I think that most of these issues will be resolved (or have been) when the porting process takes place. Is there any protocol for porting an entire library to Boost? I know that ASIO took a while for approval.

So I'm going to ask a heretical question: why do you/he want to add it to Boost? Please don't make it header only in the process or I will be forced to look at CryptoPP which is guaranteed to make babies cry. -- Sohail Somani http://uint32t.blogspot.com