Re: Bash style of if-then-else?

[Joachim Schmitz]

Pierre Gaston wrote:
> On Tue, Aug 24, 2010 at 10:25 AM, Joachim Schmitz
> <nospam.jojo@schmitz-digital.de> wrote:
> > Chris F.A. Johnson wrote:
> > > On Mon, 23 Aug 2010, Dennis Williamson wrote:
> > >
> > > > If you're writing a Bash-specific script then it's preferable to
> > > > use double square brackets (see
> > > > http://mywiki.wooledge.org/BashFAQ/031).
> > > >
> > > > if [[ -f $file ]]
> > > > then
> > > > do something
> > > > fi
> > >
> > > I'd avoid non-portable syntax unless it offers a significant
> > > advantage over standard syntax.
> > >
> > > [[ ... ]] is not standard, and offers little over the standard
> > > syntax.
> >
> > [[ ... ]] is POSIX, isn't it? As such there should be enough
> > portability and standard syntax to warrant the advantage.
> [[ ]] is reserved but not specified.

Ah, OK, found it: 
http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html

The following words may be recognized as reserved words on some 
implementations (when none of the characters are quoted), causing 
unspecified results:

       [[
      ]]
      function
      select




 Bye, Jojo