Author: hmbrand
Date: Thu Apr 29 23:51:41 2010
New Revision: 13938

Added:
   dbi/trunk/devel/
   dbi/trunk/devel/.perltidyrc-tux
   dbi/trunk/devel/README
Modified:
   dbi/trunk/MANIFEST.SKIP

Log:
Added perltidyrc for DBD::File

Modified: dbi/trunk/MANIFEST.SKIP
==============================================================================
--- dbi/trunk/MANIFEST.SKIP     (original)
+++ dbi/trunk/MANIFEST.SKIP     Thu Apr 29 23:51:41 2010
@@ -25,3 +25,4 @@
 ^t/zz_\w+_pp.t$
 ^.git
 ^git-
+^devel/

Added: dbi/trunk/devel/.perltidyrc-tux
==============================================================================
--- (empty file)
+++ dbi/trunk/devel/.perltidyrc-tux     Thu Apr 29 23:51:41 2010
@@ -0,0 +1,40 @@
+# See how far we get in getting perltidy to do the *only* right thing: my way
+
+--noblanks-before-comments
+--block-brace-tightness=0
+--brace-tightness=2
+--brace-vertical-tightness=2
+--closing-token-indentation=3
+--continuation-indentation=4
+--entab-leading-whitespace=8
+#--noindent-block-comments
+--indent-closing-brace
+--indent-columns=4
+# try with and without this:
+#--line-up-parentheses
+--maximum-line-length=80
+--opening-brace-always-on-right
+--opening-hash-brace-right
+--opening-paren-right
+--opening-square-bracket-right
+--opening-sub-brace-on-new-line
+--nooutdent-long-comments
+--nooutdent-long-quotes
+--paren-tightness=2
+--paren-vertical-tightness=2
+--nospace-for-semicolon
+--space-function-paren
+--space-keyword-paren
+--square-bracket-tightness=2
+--square-bracket-vertical-tightness=2
+--stack-closing-hash-brace
+--stack-closing-paren
+--stack-closing-square-bracket
+--stack-opening-hash-brace
+--stack-opening-paren
+--stack-opening-square-bracket
+--static-block-comment-prefix="^#"
+--static-side-comments
+# try with and without some or all of these
+#--want-break-after=". : || && and or"
+

Added: dbi/trunk/devel/README
==============================================================================
--- (empty file)
+++ dbi/trunk/devel/README      Thu Apr 29 23:51:41 2010
@@ -0,0 +1,16 @@
+DBI being maintained by several people now causes a mixture
+of styles. It has been proven that people are most productive
+when they can do things `ther way'.
+
+Tim Bunce is the owner and main maintainer of DBI. He can and
+should veto anything that is forbidden, but for now, you'll
+see different styles for the modules that have a single person
+responsible for development. You might find a perltidyrc file
+for their style in this devel/ directory. When proposing new
+features, additions, fixes or documentation, please try to do
+so in the style of that specific module.
+
+Perltidy might help.
+
+DBD::File   - H.Merijn Brand (Tux)
+   devel/.perltidyrc-tux

Reply via email to