[smtpd/qpsmtpd] 88818c: No tight square brackets or curly braces

----==_mimepart_54c9afa8277e7_75ca3ffdd1db72c0725eb
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

  Branch: refs/heads/master
  Home:   https://github.com/smtpd/qpsmtpd
  Commit: 88818c1cc90f97273b735b06ec7dfa6dd4f2604e
      https://github.com/smtpd/qpsmtpd/commit/88818c1cc90f97273b735b06ec7dfa6dd4f2604e
  Author: Jared Johnson <[email protected]>
  Date:   2015-01-27 (Tue, 27 Jan 2015)

  Changed paths:
    M .perltidyrc

  Log Message:
  -----------
  No tight square brackets or curly braces

> Likewise, the parameter -sbt=n or --square-bracket-tightness=n controls the
> space within square brackets, as illustrated below.
>
>  $width = $col[ $j + $k ] - $col[ $j ];  # -sbt=0
>  $width = $col[ $j + $k ] - $col[$j];    # -sbt=1 (default)
>  $width = $col[$j + $k] - $col[$j];      # -sbt=2
> Curly braces which do not contain code blocks are controlled by the
> parameter -bt=n or --brace-tightness=n.
>
>  $obj->{ $parsed_sql->{ 'table' }[0] };    # -bt=0
>  $obj->{ $parsed_sql->{'table'}[0] };      # -bt=1 (default)
>  $obj->{$parsed_sql->{'table'}[0]};        # -bt=2

As with PR #201, I can't find any previous concensus on introducing this
and for myself, I prefer the default.

FTR I can't find anything else in .perltidyrc that I have any bones with :)


  Commit: 575c0b09e34428ac689060a8c7425b83d3af441b
      https://github.com/smtpd/qpsmtpd/commit/575c0b09e34428ac689060a8c7425b83d3af441b
  Author: Matt Simerson <[email protected]>
  Date:   2015-01-28 (Wed, 28 Jan 2015)

  Changed paths:
    M .perltidyrc

  Log Message:
  -----------
  Merge pull request #209 from jaredj/notight

No tight square brackets or curly braces


Compare: https://github.com/smtpd/qpsmtpd/compare/04914bf4c92f...575c0b09e344
----==_mimepart_54c9afa8277e7_75ca3ffdd1db72c0725eb--