31 May
2016
31 May
'16
7:27 a.m.
What's the mnmonic significance, if any, of the u in
the bash builtin read -u for reading from a specified
file descriptor? Evidently both f and d had already been
taken in analogy to usage in some other commands.
The best I can think of is u as in "tape unit", which
was common usage back in the days of READ INPUT TAPE 5.
That would make it the work of an old timer, maybe Dave Korn?
31 May
31 May
12:55 p.m.
On 5/31/16 3:27 AM, Doug McIlroy wrote:
What's the mnmonic significance, if any, of the u
in
the bash builtin read -u for reading from a specified
file descriptor? Evidently both f and d had already been
taken in analogy to usage in some other commands.
The best I can think of is u as in "tape unit", which
was common usage back in the days of READ INPUT TAPE 5.
That would make it the work of an old timer, maybe Dave Korn?
I picked it up from ksh many years ago, and assumed at the time that it
meant `unit'.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet(a)case.edu http://cnswww.cns.cwru.edu/~chet/
2:35 p.m.
Doug McIlroy <doug(a)cs.dartmouth.edu> wrote:
What's the mnmonic significance, if any, of the u
in
the bash builtin read -u for reading from a specified
file descriptor? Evidently both f and d had already been
taken in analogy to usage in some other commands.
It seems to be a copy from ksh.
Ksh implements a private "print" builtin that also uses -u fd.
Jörg
--
EMail:joerg@schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schilling(a)fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/
http://sourceforge.net/projects/schilytools/files/'
3330
days inactive
3330
days old
2 comments
3 participants
participants (3)
-
Chet Ramey -
Doug McIlroy -
schily＠schily.net