develooper Front page | perl.perl5.porters | Postings from April 2010

Re: RFC: Perl manual pages -- update to follow the perlstyle.pod guidelines

Thread Previous | Thread Next
Tom Christiansen
April 5, 2010 06:48
Re: RFC: Perl manual pages -- update to follow the perlstyle.pod guidelines
Message ID:
In-Reply-To: Message from "H.Merijn Brand" <>
             of "Mon, 05 Apr 2010 09:50:29 +0200."

>>> Wouldn't that usage of "||" instead of "or" be a personal
>>> idiosyncrasy, then?

>> I doubt it's all that personal.

> I agree. Not that I take the same road as Tom everywhere, but the perl
> documentation is not something personal. It is written for ALL users.
> Novices and experts. As this thread already has proven that minds don't
> think alike, there is very clearly not a `better' way to write || or or
> to make things safer or more readable.

> I use both. Tom uses parens and ||, and Jari uses or. Lets keep the
> versatility in the docs. The current docs are not wrong.

Thanks.  I was beginning to wonder how soon we'd be seeing mandatory
deprecation warnings on the || operator in anticipation of its eventual
removal from the language by the Seekers of Truth and Penitence, the same
inciteful sorry insightful folks who brought us REM for comments.

The Perl distribution itself includes some 652 instances of /\|\|\s*die\b/.
That's a substantial statement in and of itself.  My own ~/scripts directory
coincidentally contains an additional 623 instances of the same.  'Nuff said.

Extirpating or even just denigrating this construct is not only a waste of
time and resources, it's also a revisionist jihad of false cleanliness
that flies in the face of widespread actual practice.


Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About