The inability to allocate mp_int variables on the stack is not as bad
as it seems. This is because the 'dp' array inside an mp_int still
needs to be allocated from the heap. An mp_new function can allocate
the mp_int structure and the 'dp' array in one shot if the number of
digits needed is known
On 03/01/2011 08:43 AM, Jean-Marc Desperrier wrote:
> Robert Relyea wrote:
>> About the
>> only use I could reasonable see for it would be to support PKCS #11
>> modules.
>
> The other use would be as an optimized base for a big num
> implementation, and that's what the original distribution says :
Robert Relyea wrote:
About the
only use I could reasonable see for it would be to support PKCS #11
modules.
The other use would be as an optimized base for a big num
implementation, and that's what the original distribution says : "ANSI C
code library that performs arbitrary precision integer
On 02/28/2011 09:03 AM, Jean-Marc Desperrier wrote:
> Hi,
>
> There was some talk last october about accessing the mp_int API from
> javascript, and so freezing it in order to make it available as a
> frozen API.
We currently don't even expose the mpi API for good reason. About the
only use I coul
On Mon, Feb 28, 2011 at 9:03 AM, Jean-Marc Desperrier wrote:
> Hi,
>
> There was some talk last october about accessing the mp_int API from
> javascript, and so freezing it in order to make it available as a frozen
> API.
>
> Nelson concluded that the one difficult point would be to freeze the mpd
Hi,
There was some talk last october about accessing the mp_int API from
javascript, and so freezing it in order to make it available as a frozen
API.
Nelson concluded that the one difficult point would be to freeze the
mpdigit structure, since it currently has machine/processor-version
dep
6 matches
Mail list logo
