Before I give mine I had a couple of minor issues.. (heh you knew that was coming didnt you?)
- For the indenting im using It(=4c<!>) to mean that I use tabs, but have them set to be displayed as four spaces and that my editor automatically converts leading spaces to such tabs and it automatically truncates trailing spaces. Sorry if I didnt follow the code, hopefully you havent finished your parser for this yet ;-)
- For parens im using -0.5 because I use the minimum number of parens that keeps my codes meaning clear, but I dont try to explicitly avoid them.
- For references I used R1.5 because I often call vars "array_ref" or the like, but I dont put "ref" in anything like all variables references.
- Im using d0 for the dummy name question, assuming that "a" and "b" also includes safer var names like "i","j","x","y"
- I added the keyword "tidy" to your end block, because I rotuinely run my code through perltidy.
more compliant with the updated spec. I stand by the tidy bit though.
It=4! Os1 ;0 S,>.+**<=><&&><and><gt>++<==> B1 L1 C2
P-.5 N>e R2 Vl(en)c1a1p(s0h0a0)r1d.5 Hsw1 sub-main-tidy
BTW, two thoughts regarding perltidy, the first is that you might have a look there for even more options for a later version of the perl geek style code, and on the other hand wouldnt it be cool if you could feed this style blcok into perltidy and have it behave accordingly? Now theres a nifty little hack that you could do that would put your style code a touch above some of the other codes (at least in terms of practicality.)
Cheers Juerd, good post!
Yves / DeMerphq
Writing a good benchmark isnt as easy as it might look.