Abstract
Of all of the aspects of language design, input-output (or I/O) is regarded as the most distasteful. One reason for this is likely that it is impossible to make the design of this part of a language entirely independent of the computer’s characteristics. Some language designers have gone so far as to put their collective heads in the sand and not define input-output at all. The ALGOL60 team was an early sinner in this regard, and more recently the Euclid design group has done the same. But most language designers have faced up to the fact that it is better to design as much of the I/O in a machine independent manner, than to have the entire facility patched on by the language implementors.
“A PRINT statement does not imply that printing will occur, and a WRITE statement does not imply that printing will not occur. lines 1046–1048”, FORTRAN77 Manual
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 1984 Computer Science Press
About this chapter
Cite this chapter
Horowitz, E. (1984). Input-Output. In: Fundamentals of Programming Languages. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-69406-6_11
Download citation
DOI: https://doi.org/10.1007/978-3-642-69406-6_11
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-69408-0
Online ISBN: 978-3-642-69406-6
eBook Packages: Springer Book Archive