Re^2: Your Favorite Options for Perltidy

Perltidy can also be used for other things than code formatting. In fact, it can be bloody helpful. Take the following heartsinking error message:

Missing right curly or square bracket at ccpd.pl line 1102, at end of 
+line
syntax error at ccpd.pl line 1102 at EOF
[download]

Bugger. So where is the missing curly brace? Dunno. Have no fear, for Perltidy will tell me in the error file it creates.

The most recent un-matched '{' is on line 567
567: sub createAuthMessage {
[download]

Now that rocks.

-- vek --

Comment on Re^2: Your Favorite Options for Perltidy Select or Download Code

Replies are listed 'Best First'.
Re^3: Your Favorite Options for Perltidy by ambrus (Abbot) on Nov 06, 2005 at 10:42 UTC
An editor can help there too: I jump to the EOF where the error appears, insert a closing brace, and jump to the matching brace. However, an even more efficent way to find the missing braces is when the interpreter guesses its place from the indentation of the code (even though the indentation has no semantical meanning). The MzScheme interpreter can do this, and usually guesses right. (I hope perl6 will be able to do this too.) If, however, you reformat the code with an indenter, then the indents will follow the braces you've put there, not the way you think the code should be indented, so then indentation can't provide a clue to the interpreter.	[reply]
Re^3: Your Favorite Options for Perltidy by Anonymous Monk on Nov 06, 2005 at 11:49 UTC
That rocks indeed! What command do you use to generate that last message? And in what environment?	[reply]
Re^4: Your Favorite Options for Perltidy by vek (Prior) on Nov 06, 2005 at 17:16 UTC
You don't need a special command. Perltidy will create an error file. `shell>perltidy ccpd.pl Please see file ccpd.pl.ERR! shell>view ccpd.pl.ERR` [download] -- vek --	[reply] [d/l]