documentation on internals not up to date

2018-04-09 Thread Trevor Spiteri
Hello, The documentation on the internals is still saying that: > Currently there's always at least one limb allocated, so for instance mpz_set_ui never needs to reallocate... But in the current repository state, that is no longer the case. Regards. Trevor Spiteri _

Re: documentation on internals not up to date

2018-04-26 Thread Marco Bodrato
Ciao, Il Lun, 9 Aprile 2018 5:30 pm, Trevor Spiteri ha scritto: > The documentation on the internals is still saying that: [...] > But in the current repository state, that is no longer the case. Yes, we currently have: Currently there's always at least one limb allocated, so for instance @code{

Re: documentation on internals not up to date

2018-04-26 Thread Niels Möller
"Marco Bodrato" writes: > What about the following? > > Currently there's always at least one readable limb, so for instance > @code{mpz_get_ui} can fetch @code{_mp_d[0]} unconditionally (though its > value is then only wanted if @code{_mp_size} is non-zero). Maybe change "is only wanted if" to

Re: documentation on internals not up to date

2018-04-26 Thread Marco Bodrato
Ciao, Il Ven, 27 Aprile 2018 7:21 am, Niels Möller ha scritto: > Since this is the section on internals, I think it's appropriate to > document. _mp_alloc == 0 and _mp_size == 0 means that value is zero, and ... I'd move the discussion on gmp-devel. Ĝis, m -- http://bodrato.it/papers/ ___