Xref: utzoo comp.unix.wizards:19433 comp.unix.questions:17901 Path: utzoo!attcan!uunet!samsung!shadooby!mailrus!wuarchive!texbell!sugar!ficc!peter From: peter@ficc.uu.net (Peter da Silva) Newsgroups: comp.unix.wizards,comp.unix.questions Subject: Re: Question about GETOPT(3) Message-ID: <7077@ficc.uu.net> Date: 21 Nov 89 21:42:23 GMT References: <7043@ficc.uu.net> <110@amix.commodore.com> Reply-To: peter@ficc.uu.net (Peter da Silva) Organization: Xenix Support, FICC Lines: 28 > In article <7043@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes: > >What syntax should the shell use for /dev/stdin? > > command &1 # stdout is an argument to command. > '&' in the shell is an actual separator of commands, that is: Yes, I know. So? > command >&1 (and command && command) > does not break '&' normal use because it is used in the twople '>&' So &1 would be a similar dipthong, with no white space allowed. It's no greater a syntax problem than the distinction between !cmd 2 > file! and !cmd 2> file!. > I doubt the general usefullness of having the shell expand any sequence of > symbols to '/dev/stdin' (except in globbing: /dev/stdi* :-). And how about in variable expansion, command line substitution, and shell functions? -- `-_-' Peter da Silva . 'U` -------------- +1 713 274 5180. "I agree 0bNNNNN would have been nice, however, and I sure wish X3J11 had taken time off from rabbinical hairsplitting to add it." -- Tom Neff