Author: ericwilhelm
Date: Sat Sep 27 19:47:46 2008
New Revision: 11888

Added:
   Module-Build/trunk/.perltidyrc

Log:
.perltidyrc - checking-in for comment


Added: Module-Build/trunk/.perltidyrc
==============================================================================
--- (empty file)
+++ Module-Build/trunk/.perltidyrc      Sat Sep 27 19:47:46 2008
@@ -0,0 +1,49 @@
+--maximum-line-length=72
+
+# (note an indent is an indent, so no "continuation indents")
+--indent-columns=2
+
+# I usually want blank lines before comments, but it is not worth
+# fighting with perltidy's inability to recognize blocks.
+--noblanks-before-comments
+
+--space-after-keyword="and or eq ne"
+# the paren+args are part of the keyword
+--nospace-after-keyword="if else elsif until unless while for foreach return 
switch case given when"
+
+# break after the operator so it doesn't look like a syntax error
+--want-break-after=". << >> -> && || and or"
+
+# we don't put spaces after parens in english
+--paren-tightness=2
+--block-brace-tightness=2
+--square-bracket-tightness=2
+--brace-tightness=2
+
+# who uses space before the peterbuilt?
+--nohanging-side-comments
+--nospace-for-semicolon
+--indent-block-comments
+--minimum-space-to-comment=1
+# never outdent
+--nooutdent-long-lines
+
+# these are currently broken wrt closing indent :-(
+#--stack-opening-token
+#--stack-closing-token
+
+# still pondering this one -- seems to help in some cases, break others
+#--nodelete-old-newlines
+
+# Eric wants --break-at-correct-breakpoints
+#--break-at-old-comma-breakpoints
+#--break-at-old-trinary-breakpoints
+#--break-at-old-logical-breakpoints
+#--break-at-old-keyword-breakpoints
+
+#--closing-token-indentation=0
+--noindent-closing-brace
+--noindent-closing-paren
+
+#--vertical-tightness-closing=0
+--nooutdent-long-quotes

Reply via email to