Re: return from function doesn't work when used in tail of pipeline

On Thu, 12 Aug 2010 08:16:21 -0400, Greg Wooledge wool...@eeg.ccf.org wrote: You already know the reason it behaves the way it does, so I'm not quite sure what answer you expect to receive. It's not a bug -- it's the normal behavior of every shell. imadev:~$ sh -c 'f() { (return 0); return

return from function doesn't work when used in tail of pipeline

Configuration Information [Automatically generated, do not change]: Machine: i486 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale'

Re: ${parameter+word} not documented in bash.info or bash(1)

Bob == Bob Proulx b...@proulx.com writes: Bob [...] Let me suggest that something similar to the following Bob addition would help here. Bob is unset or null; omitting the colon (':') results in a Bob test only for a parameter that is unset. Bob Then searches on : would

Re: ${parameter+word} not documented in bash.info or bash(1)

Paul == Paul Jarc p...@po.cwru.edu writes: Paul Martin Schwenke mar...@meltin.net wrote: Neither bash.info or bash(1) documents parameter expansion of the form: ${parameter+word} Paul It's documented, but it's easy to miss. Just before the Paul list

${parameter+word} not documented in bash.info or bash(1)

I'm running bash 3.2.39(1)-release (under Ubuntu 8.04 (Hardy) GNU/Linux). Neither bash.info or bash(1) documents parameter expansion of the form: ${parameter+word} This is different to ${parameter:+word}, is clearly implemented by bash and is documented in the standard (The Open Group Base