Re: [9fans] Duff's rc paper: Why awk?

[Rudolf Sykora]

 plan 9 sed reads a second line before quitting (note the def in the example
 below); sed does not work.

Is there any good reason for this difference between plan9 and gnu behaviour?

Thanks!
Ruda

Re: [9fans] Duff's rc paper: Why awk?

[markus schnalke]

[2013-06-11 14:24] Rudolf Sykora rudolf.syk...@gmail.com
  plan 9 sed reads a second line before quitting (note the def in the 
  example
  below); sed does not work.

Erik, thanks for the explanation.

However, the man page states:

q   Quit. Branch to the end of the script. Do not start a new cycle.

Thus, this is a bit odd.


 Is there any good reason for this difference between plan9 and gnu behaviour?

It looks a bit like the bug described in the man page, although input is read
from the terminal, not from a pipe.

http://plan9.bell-labs.com/magic/man2html/1/sed


meillo

Re: [9fans] Duff's rc paper: Why awk?

[erik quanstrom]

 I've read [0], which is enlightening btw, but there is one thing,
 in Section 27, which I don't understand: Why is awk(1) used there?
 
   fn read{
   $1=`{awk '{print;exit}'}
   }
 
 [0] http://static.tobold.org/rc/rc-duff.html
 
 I rather would have used sed(1), which is less distracting in this
 case:
 
   fn read{
   $1=`{sed q}
   }
 
 This use of awk is unexpected to me, it draws my attention on it,
 thus I'm searching for the strange hidden detail that might be
 emphasized. (Such as the use of `if not' instead of `else'.) But I
 can't find it.
 
 Maybe there is no such hidden detail. Maybe there is no real
 reason behind the use of awk here. I'm not really sure ...

plan 9 sed reads a second line before quitting (note the def in the example
below); sed does not work.

- erik
--
; fn read{
$1=`{sed q}
echo read `{whatis $1}
}
; read x
abc
def
read x=abc
; fn read{
$1=`{awk '{print;exit}'}
echo read `{whatis $1}
}
; read x
abc
read x=abc