Re: What shell feature did surprise you?

Stephane CHAZELAS wrote:

2011-05-27, 13:01(+02), Janis Papanagnou:

Just remembered... - I had been surprised by a function definition
with (subshell-)parenthesis instead of curly braces around the
function body ; with all consequences, as in the subsequent example...

In all Bourne-like shells but bash, the syntax is

foo() any-command

so can be

foo() echo test
f() g() { echo test; }
foo() { ...; }
foo() ( ...; )
foo() for i do
echo "<$i>"; done

bash and POSIX only allow compound commands (so all but the
first 2 above).

In POSIX the syntax is:

fname() compound-command[io-redirect ...]

I can remember being surprised about that io-redirect when I came
across it in the standard in the mid 1990's.

$ ls
$ func() { echo foo; } > "$func_out"
$ func_out=file1; func
$ func_out=file2; func
$ ls
file1 file2

--
Geoff Clare <netnews@xxxxxxxxxxxxx>

.

Relevant Pages

  • Re: What Data Structure should I use?
    ... I have a function called foo() and it accepts objects of classes as ... how do I define the parameter in the function definition? ... public void foo(Ftr paramname) {... ...
    (comp.lang.java.programmer)
  • Re: What shell feature did surprise you?
    ... foo() any-command ... fg{echo test;} ... In POSIX the syntax is: ... performs the redirection at the time of the function definition ...
    (comp.unix.shell)
  • Re: saving/restoring function def (bash)
    ... How can I save existing function definition of foo ... redefine foo() differently but keep the old definition around). ... it involves a fork. ...
    (comp.unix.shell)
  • Re: saving/restoring function def (bash)
    ... How can I save existing function definition of foo ... redefine foo() differently but keep the old definition around). ... echo FOO ...
    (comp.unix.shell)
  • legality of signature changes of callback functions
    ... Is it legal to implement the callback functions as ... taking a void* for this argument. ... typedef struct Foo Foo; ... Func func= MyFunc; ...
    (comp.lang.c)