| Line 35... |
Line 35... |
| 35 |
\code{\link{sprintf}} and related functions. In these cases, the
|
35 |
\code{\link{sprintf}} and related functions. In these cases, the
|
| 36 |
translation must give a compatible format or an error will be
|
36 |
translation must give a compatible format or an error will be
|
| 37 |
generated when the message is displayed.
|
37 |
generated when the message is displayed.
|
| 38 |
|
38 |
|
| 39 |
The rules for compatibility differ between C and \R in several ways. C
|
39 |
The rules for compatibility differ between C and \R in several ways. C
|
| 40 |
supports several conversions not supported by \R, namely \code{c, u,
|
40 |
supports several conversions not supported by \R, namely \code{c},
|
| 41 |
p, n}. It is allowed in C's \code{sprintf()} function to have more
|
41 |
\code{u}, \code{p}, \code{n}. It is allowed in C's \code{sprintf()}
|
| 42 |
arguments than are needed by the format string, but in \R the counts
|
42 |
function to have more arguments than are needed by the format string,
|
| 43 |
must match exactly. \R requires types of arguments to match, whereas
|
43 |
but in \R the counts must match exactly. \R requires types of
|
| 44 |
C will do the display whether it makes sense or not.
|
44 |
arguments to match, whereas C will do the display whether it makes
|
| - |
|
45 |
sense or not.
|
| 45 |
|
46 |
|
| 46 |
These functions compromise on the testing as follows. The additional
|
47 |
These functions compromise on the testing as follows. The additional
|
| 47 |
formats allowed in C are accepted, and all differences in argument
|
48 |
formats allowed in C are accepted, and all differences in argument
|
| 48 |
type or count are reported. As a consequence some reported
|
49 |
type or count are reported. As a consequence some reported
|
| 49 |
differences are not errors.
|
50 |
differences are not errors.
|