2 This is a partial "wish-list" of features to add and things to do. All
3 of these are of interest, but there is no particular schedule for
6 Improved Vertical Alignment
7 There are many opportunities for improving vertical alignment.
9 More options for controling placement of opening/closing tokens
10 Many have requested even more options to control opening and closing
13 improved ?: formatting
14 An indentation level should be associated with ?: statements. This will
15 make nested ?: statements more readable.
17 improved internal if/unless formatting
18 Consider giving internal if/unless statements an additional level of
19 indentation. This would avoid running out of indentation levels.
20 Suggested by Jeff Armstorng. For example, we would like the 'ands' in
21 the following statement to be indented more than the if:
23 return $ship->chargeWeapons("phaser-canon")
24 if $encounter->description eq 'klingon'
25 and $ship->firepower >= $encounter->firepower
26 and $location->status ne 'neutral';
28 enable -ole under Windows
29 This only works under unix (or cygwin) at present. It doesn't work for
30 Windows versions, such as Active State, because they change line endings
34 A FAQ is needed to explain some of the more subtle formatting issues,
35 and to give examples of different styles.
37 The -formatter callback object documentation is incomplete.
40 The HTML writer does not colorize interpolated identifiers in here
41 documents or quoted strings. The tokenizer outputs interpolation
42 information for here docs; it still needs to be updated to do this for
43 multi-line quotes. Then code needs to be written to scan for and markup
46 Automatic style detection
47 It would be nice to write a program to read a sample of perl code and
48 write an approximate .perltidyrc file for that style.
50 Things which have been suggested but will not be done
51 Recursive file processing
52 A -r flag might be nice, but this is probably best handled by an
53 exterior shell script.