Re: Re: Re: Re: Re: Crash Course in POD

[IlyaM]

I used to be like you, not liking inline pod, but now I feel its the way to go (tastes change)

Funny... my taste changed in the opposite direction.

My taste changed a couple of times in both directions :)

Related observation: programmers who don't use editors which do POD highlighting hate inline POD as it mixes with source code. If you have decent editor like emacs it is less a problem as it clearly visually separates code from documentation.

--
Ilya Martynov, [e-mail]
CTO IPonWEB (UK) Ltd
Quality Perl Programming and Unix Support UK managed @ offshore prices - http://www.iponweb.net
Personal website - http://martynov.org

[Abigail-II]

You mean, it colour codes your text? I hate *that*. I don't like my code to look like a christmas tree. And, IMO, colourcoding editors do not contribute to writing clear code. If you need your code to be coloured to make sense out of it, then there's something wrong with your code. Good code doesn't need colours.

Abigail

[crenz]

Colour-coding is definitely a matter of style. Personally, I very much like simple colour-coding. I find that even just colouring strings, numbers and comments makes code so much more readable. But maybe I'm not writing good code :)

Apart from the subject matter, I find it interesting how you phrase your argument. Inferring that code will look like a christmas tree if you use the ever-slightest colour-coding definitely is an unusual chain of reasoning... Good arguments don't need strange reasons to support them.

[zby]

For me colour is a syntax shortcut. It shorcirquits some brainpaths and lets you parse the code with less effort.

[Juerd]

Related observation: programmers who don't use editors which do POD highlighting hate inline POD as it mixes with source code.

I'm different then. My editor does color pod differently, yet I still dislike inline pod. I also dislike many-line comments.

Juerd
- http://juerd.nl/
- [e-mail] (do not use).