|Think about Loose Coupling|
(heh you knew that was coming didnt you?)
I was afraid of that, yes :)
* 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.
I'll use just It=4!, meaning: "Indenting by tabs, but they are displayed as 4 columns of nothingness. I have my editor force (exclamation mark was stolen from vim) existing code to follow my style (convert spaces to tabs, in this case)". :)
# Sorry if I didnt follow the code, hopefully you havent finished your parser for this yet ;-)
I don't like parsing/parsed geek codes, so I will leave that up to someone else.
# 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.
Unlike with ++++ and ---, you can have floating point numbers. I like that idea. Will add :)
* I added the keyword "tidy" to your end block, because I rotuinely run my code through perltidy.
The end stuff was only to indicate order in a file, not programming order.
Hmm, I really meant that whitespace to be in between items. But even that is a matter of style ;) Maybe sub-main is going to screw some parsers, but seeing your code, I'm glad I picked uppercased letters just before hitting submit :)
and on the other hand wouldnt it be cool if you could feed this style blcok into perltidy and have it behave accordingly?
That's just SICK, but a nice idea :)
Cheers jured, good post!
Thanks, but please s/jured/Juerd/ ;)