Atmel CAVR-4 Manual De Usuario
![Atmel](https://files.manualsbrain.com/attachments/0369829915bda09f9c2e00fb805a7753579683b5/common/fit/150/50/8d2bf08978ec3e5bc63f4343ac5e91ce8d0e40045619fa520d910d64af8f/brand_logo.png)
CAVR-4
266
Descriptions of implementation-defined behavior
AVR® IAR C/C++ Compiler
Reference Guide
fmod() functionality (7.5.6.4)
If the second argument to
fmod()
is zero, the function returns
NaN
;
errno
is set to
EDOM
.
signal() (7.7.1.1)
The signal part of the library is not supported.
Note: Low-level interface functions exist in the library, but will not perform anything.
Use the template source code to implement application-specific signal handling. See
Signal and raise, page 73.
Use the template source code to implement application-specific signal handling. See
Signal and raise, page 73.
Terminating newline character (7.9.2)
stdout
stream functions recognize either
newline
or
end
of
file
(EOF)
as the
terminating character for a line.
Blank lines (7.9.2)
Space characters written to the
stdout
stream immediately before a newline character
are preserved. There is no way to read the line through the
stdin
stream that was
written through the
stdout
stream.
Null characters appended to data written to binary streams (7.9.2)
No null characters are appended to data written to binary streams.
Files (7.9.3)
Whether a write operation on a text stream causes the associated file to be truncated
beyond that point, depends on the application-specific implementation of the low-level
file routines. See File input and output, page 70.
beyond that point, depends on the application-specific implementation of the low-level
file routines. See File input and output, page 70.
remove() (7.9.4.1)
The effect of a remove operation on an open file depends on the application-specific
implementation of the low-level file routines. See File input and output, page 70.
implementation of the low-level file routines. See File input and output, page 70.
rename() (7.9.4.2)
The effect of renaming a file to an already existing filename depends on the
application-specific implementation of the low-level file routines. See File input and
output, page 70.
application-specific implementation of the low-level file routines. See File input and
output, page 70.