1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
|
From: Sam James <sam@gentoo.org>
Date: Sat, 6 Nov 2021 00:34:22 +0000
Subject: [PATCH] Revert doc changes from mpfr-4.1.0-patch10
We don't want to invoke texinfo via maintainer-mode because
of some (somewhat minor) changes to the manual from patch10.
See: https://archives.gentoo.org/gentoo-releng-autobuilds/message/c2dd39fc4ebc849db6bb0f551739e2ed
Signed-off-by: Sam James <sam@gentoo.org>
---
doc/mpfr.info | 46 +++++++++++++++++++++-------------------------
doc/mpfr.texi | 6 ------
2 files changed, 21 insertions(+), 31 deletions(-)
diff --git a/doc/mpfr.info b/doc/mpfr.info
index 062c0c4..264896d 100644
--- a/doc/mpfr.info
+++ b/doc/mpfr.info
@@ -3217,11 +3217,7 @@ destroying, garbaging) is left to the application.
Each function in this interface is also implemented as a macro for
efficiency reasons: for example ‘mpfr_custom_init (s, p)’ uses the
-macro, while ‘(mpfr_custom_init) (s, p)’ uses the function. Note that
-the macro may evaluate arguments multiple times (or none). Moreover,
-macros implementing functions with the ‘void’ return type may not be
-used in contexts where an expression is expected, e.g., inside
-‘for(...)’ or before a comma operator.
+macro, while ‘(mpfr_custom_init) (s, p)’ uses the function.
Note 1: MPFR functions may still initialize temporary floating-point
numbers using ‘mpfr_init’ and similar functions. See Custom Allocation
@@ -4583,13 +4579,13 @@ Function and Type Index
(line 115)
* mpfr_csch: Transcendental Functions.
(line 180)
-* mpfr_custom_get_exp: Custom Interface. (line 80)
-* mpfr_custom_get_kind: Custom Interface. (line 70)
-* mpfr_custom_get_significand: Custom Interface. (line 75)
-* mpfr_custom_get_size: Custom Interface. (line 41)
-* mpfr_custom_init: Custom Interface. (line 45)
-* mpfr_custom_init_set: Custom Interface. (line 52)
-* mpfr_custom_move: Custom Interface. (line 89)
+* mpfr_custom_get_exp: Custom Interface. (line 76)
+* mpfr_custom_get_kind: Custom Interface. (line 66)
+* mpfr_custom_get_significand: Custom Interface. (line 71)
+* mpfr_custom_get_size: Custom Interface. (line 37)
+* mpfr_custom_init: Custom Interface. (line 41)
+* mpfr_custom_init_set: Custom Interface. (line 48)
+* mpfr_custom_move: Custom Interface. (line 85)
* MPFR_DECL_INIT: Initialization Functions.
(line 77)
* mpfr_digamma: Transcendental Functions.
@@ -5169,19 +5165,19 @@ Node: Exception Related Functions145661
Node: Memory Handling Functions155904
Node: Compatibility with MPF157792
Node: Custom Interface160961
-Node: Internals165852
-Node: API Compatibility167396
-Node: Type and Macro Changes169344
-Node: Added Functions172527
-Node: Changed Functions177334
-Node: Removed Functions184693
-Node: Other Changes185423
-Node: MPFR and the IEEE 754 Standard187124
-Node: Contributors189741
-Node: References192880
-Node: GNU Free Documentation License194761
-Node: Concept Index217355
-Node: Function and Type Index223428
+Node: Internals165592
+Node: API Compatibility167136
+Node: Type and Macro Changes169084
+Node: Added Functions172267
+Node: Changed Functions177074
+Node: Removed Functions184433
+Node: Other Changes185163
+Node: MPFR and the IEEE 754 Standard186864
+Node: Contributors189481
+Node: References192620
+Node: GNU Free Documentation License194501
+Node: Concept Index217095
+Node: Function and Type Index223168
End Tag Table
diff --git a/doc/mpfr.texi b/doc/mpfr.texi
index b26555a..54b6aa8 100644
--- a/doc/mpfr.texi
+++ b/doc/mpfr.texi
@@ -3817,12 +3817,6 @@ to the application.
Each function in this interface is also implemented as a macro for
efficiency reasons: for example @code{mpfr_custom_init (s, p)}
uses the macro, while @code{(mpfr_custom_init) (s, p)} uses the function.
-Note that the macro may evaluate arguments multiple times (or none).
-Moreover, macros implementing functions with the @code{void} return type
-may not be used in contexts where an expression is expected, e.g., inside
-@code{for(...)} or before a comma operator.
-@c These limitations with macros cannot be avoided in a C90 compatible way.
-@c In the future, inline functions could be used.
Note 1: MPFR functions may still initialize temporary floating-point numbers
using @code{mpfr_init} and similar functions. See Custom Allocation (GNU MP)@.
--
2.33.1
|
GitWeb