Whatever gets the job done, or will get future jobs done more quickly. Attribute::Property exists for a reason, but I normally don't use attributes much. My perl scripts are not threaded, although I like how forks gives me similar functionality with good old CoW forks. I'd use extensions like Switch if I felt any need to, but I'll probably not use it as long as series of ifs and elsifs and hashes of coderefs do what I want.

Although you're not interested in this information, I'd like to note that I'm a 4-space indenter and that I like cuddled elses. My code doesn't have much parenthesis, but it's not something I try to avoid; I'm just lazy and don't want to type much.

I'm not a strong believer in object orientation, and like that Perl lets me choose the way I code. In practice, I do use OO a lot. I like code to be clear and dislike redundancy. Because I don't want to limit myself in what I do, I always assume that whoever will maintain my stuff speaks Perl fluently. Many others avoid constructs with map, don't touch certain regex assertions, write extremely_verbose_variable_names and spell out every idiom used, just so that any moron can maintain their code. I hate when people do that: just be yourself and code the way you want to; use the features that you think are appropriate and don't be afraid of using things that newbies would avoid.

My Perl dialect? I have no idea, and don't really care. I'm happy if perl does what I want and I can still read my own code in a few months from $now.

Juerd
- http://juerd.nl/
- spamcollector_perlmonks@juerd.nl (do not use).