X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=TODO;h=bb1f87437ca0513e9afcfbb5b1c5b2de608bbf2b;hb=5c180637bf79ffc2af10f6654d308ce39e2f1f67;hp=4b6341fb51992fa4cf760ec5a44240cd6e886e68;hpb=8aa69fbac36a21cad0a1c0d5b3452a546d427d7f;p=perltidy.git

diff --git a/TODO b/TODO
index 4b6341f..bb1f874 100644
--- a/TODO
+++ b/TODO
@@ -1,25 +1,30 @@
 Perltidy TODO List
-    This is a partial "wish-list" of features to add and things to do. All
-    of these are of interest, but there is no particular schedule for
-    implementing them.
+    This is a partial "wish-list" of features to add and things to do.
 
-  Improved Vertical Alignment
-    There are many opportunities for improving vertical alignment.
+  -b does not work through the Tidy module
+    The use of -b in the following does not work:
+
+       use Perl::Tidy ();
+       use File::Spec;
+
+       my $file = File::Spec->catfile( $dir,
+          $filename );
 
-  improved ?: formatting
-    An indentation level should be associated with ?: statements. This would
-    make nested ?: statements more readable.
+       Perl::Tidy::perltidy(
+          source     => $file,
+          argv        => '-b',
+          perltidyrc => $perltidyrc,
+       );
 
-  improved internal if/unless formatting
-    Consider giving internal if/unless statements an additional level of
-    indentation. This would avoid running out of indentation levels.
-    Suggested by Jeff Armstorng. For example, we would like the 'ands' in
-    the following statement to be indented more than the if:
+    A temporary workaround is:
 
-        return $ship->chargeWeapons("phaser-canon")
-          if $encounter->description eq 'klingon'
-          and $ship->firepower >= $encounter->firepower
-          and $location->status ne 'neutral';
+       Perl::Tidy::perltidy(
+          argv        => "-b $file",
+          perltidyrc => $perltidyrc,
+       );
+
+  Improved Vertical Alignment
+    There are still many opportunities for improving vertical alignment.
 
   Documentation
     A FAQ is needed to explain some of the more subtle formatting issues,
@@ -34,12 +39,8 @@ Perltidy TODO List
     multi-line quotes. Then code needs to be written to scan for and markup
     identifiers.
 
-  Automatic style detection
-    It would be nice to write a program to read a sample of perl code and
-    write an approximate .perltidyrc file for that style.
-
 Things which have been suggested but will not be done
   Recursive file processing
-    A -r flag might be nice, but this is probably best handled by an
-    exterior shell script.
+    A -r flag might be nice, but this is best handled by an exterior shell
+    script.