diff options
| author | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2017-08-21 12:31:22 +0000 |
|---|---|---|
| committer | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2017-08-21 12:31:22 +0000 |
| commit | f29c3ff29bb98e3ae6674000900b4017aa95a4be (patch) | |
| tree | 1d9beaf606ba01ed9d175b1a3ef9c76990c9b183 | |
| parent | 356f7e2d655a38254903344210bf94dad0d82e82 (diff) | |
| download | mpfr-f29c3ff29bb98e3ae6674000900b4017aa95a4be.tar.gz | |
[doc/mpfr.texi] Slightly changed the paragraph about memory allocation
by MPFR (after a discussion with PZ).
git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/branches/3.1@11633 280ebfd0-de03-0410-8827-d642c229c3f4
| -rw-r--r-- | doc/mpfr.texi | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/mpfr.texi b/doc/mpfr.texi index c3728b167..8de7cad68 100644 --- a/doc/mpfr.texi +++ b/doc/mpfr.texi @@ -943,7 +943,7 @@ with an implementation-defined TLS specifier). @c is just a GCC extension. There is currently no clear documentation @c about TLS variable initialization. -By default, MPFR currently uses the GMP memory allocators +By default, MPFR uses the GMP memory allocators @ifinfo (@pxref{Custom Allocation,,, gmp.info,GNU MP}) @end ifinfo @@ -956,9 +956,9 @@ clean-up if the GMP allocators had to be changed (by the application or another library), the current GMP allocators are memorized the first time they are used by MPFR, and MPFR will always use these allocators. This means that the allocators need to remain valid as long as MPFR is -used. To avoid this requirement, MPFR 4 will handle memory allocation -differently, and applications that change the allocators may have to be -slightly modified. +used. To avoid this requirement, future versions may handle memory +allocation differently, and applications that change the allocators +may have to be slightly modified. @node MPFR Interface, API Compatibility, MPFR Basics, Top @comment node-name, next, previous, up |