Hi Guys, Is anybody actively developing the Crypto library implementation in the vault? I ask because I'd like to know if there would be a possibility to make it a header-only implementation. This should make it a better/easier fit for adding cryptographic hash support to Boost. Have a good day everyone. -- Dean Michael C. Berris Software Engineer, Friendster, Inc.
Hi, I'm developing this library, it's possible to make it header-only, but it is not a priority for me. I want the header-only path to be enabled via a preprocessor switch (or make that the default and add the switch for the lib path). Kevin
Hi Kevin, On Fri, Aug 8, 2008 at 5:50 PM, Kevin Sopp <baraclese@googlemail.com> wrote:
Hi,
I'm developing this library, it's possible to make it header-only, but it is not a priority for me.
Nice. Thanks. Are you continuing the development of this library? For instance, I know that there's a section dedicated for public-key cryptography (which I'm not sure you've already implemented). Do you have an estimated time of completion at least of the documentation?
I want the header-only path to be enabled via a preprocessor switch (or make that the default and add the switch for the lib path).
This sounds alright (like the Boost.Date_Time approach) but I don't see why you'd like to create an external lib if it's already available header-only. I must be missing something. Thanks again, and I look forward to progress in this library. :) -- Dean Michael C. Berris Software Engineer, Friendster, Inc.
Are you continuing the development of this library?
For instance, I know that there's a section dedicated for public-key cryptography (which I'm not sure you've already implemented). Do you have an estimated time of completion at least of the documentation?
I'm working on a multi-precision integer library which is necessary for public key cryptography. After that library is done I will come back to the crypto library.
This sounds alright (like the Boost.Date_Time approach) but I don't see why you'd like to create an external lib if it's already available header-only.
I must be missing something.
Because linking to the library should reduce the compile time.
Thanks again, and I look forward to progress in this library. :)
So do I ;-) Kevin
On Mon, Aug 11, 2008 at 4:00 AM, Kevin Sopp <baraclese@googlemail.com> wrote:
Are you continuing the development of this library?
For instance, I know that there's a section dedicated for public-key cryptography (which I'm not sure you've already implemented). Do you have an estimated time of completion at least of the documentation?
I'm working on a multi-precision integer library which is necessary for public key cryptography. After that library is done I will come back to the crypto library.
Nice. Is this multi-precision integer library going to be submitted for Boost inclusion as well?
This sounds alright (like the Boost.Date_Time approach) but I don't see why you'd like to create an external lib if it's already available header-only.
I must be missing something.
Because linking to the library should reduce the compile time.
Hmmm... Is that the only reason why you'd want to not make it header-only in the first place?
Thanks again, and I look forward to progress in this library. :)
So do I ;-)
Nice. :D -- Dean Michael C. Berris Software Engineer, Friendster, Inc.
participants (2)
-
Dean Michael Berris -
Kevin Sopp