Commit ed146156 by Thomas Koenig Committed by Thomas Koenig

gfortran.texi: Remove reservations about I/O usability.


2005-10-30  Thomas Koenig  <Thomas.Koenig@online.de>

	* gfortran.texi:  Remove reservations about I/O usability.  Document
	that array intrinsics mostly work.

From-SVN: r106252
parent dda0f764
2005-10-30 Thomas Koenig <Thomas.Koenig@online.de>
* gfortran.texi: Remove reservations about I/O usability. Document
that array intrinsics mostly work.
2005-10-30 Tobias Schl"uter <tobias.schlueter@physik.uni-muenchen.de> 2005-10-30 Tobias Schl"uter <tobias.schlueter@physik.uni-muenchen.de>
* gfortran.texi: Move license stuff to back. Add information * gfortran.texi: Move license stuff to back. Add information
......
...@@ -420,29 +420,10 @@ whether to use inline code (good for small arrays as no function call ...@@ -420,29 +420,10 @@ whether to use inline code (good for small arrays as no function call
overhead occurs) or generate function calls (good for large arrays as it overhead occurs) or generate function calls (good for large arrays as it
allows use of hand-optimized assembly routines, SIMD instructions, etc.) allows use of hand-optimized assembly routines, SIMD instructions, etc.)
The IO library is still under development. The following features should be The IO library is in a mostly usable state. Unformatted I/O for
usable for real programs: @code{REAL(KIND=10)} variables is currently not recommended.
@itemize @minus Array intrinsics mostly work.
@item List directed
@item Unformatted sequential
@end itemize
Usable with bugs:
@itemize @minus
@item Formatted sequential ('T' edit descriptor, and others)
@end itemize
Not recommended:
@itemize @minus
@item Unformatted direct access
@item Formatted direct access
@end itemize
Many Fortran programs only use a small subset of the available IO
capabilities, so your mileage may vary.
@node Proposed Extensions @node Proposed Extensions
@section Proposed Extensions @section Proposed Extensions
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment