Re^4: Tao Perl Ching - The Scripture of the Way of Perl

[legato]

There are good reasons for many of those things. Vars begins with an upper-case V because vars is a Perl reserved word. All the other functions use lower-first casing, so better to make the one exception than change the entire module's syntax.

The prefixed minus is familiar to me from another language (I can't remember which, now) -- it's not an attempt to make them look like shell arguments, but rather a very common style; I suspect the author(s) of CGI.pm were used to using and seeing that style for named parameters. Because of this, when my functions accept named parameters, I use Params::Validate to normalize the keys, allowing but not requiring the prefixed minus.

[Juerd]

There are good reasons for many of those things. Vars begins with an upper-case V because vars is a Perl reserved word.

It may be a reason, but it certainly is not a GOOD reason. It's an awful one. If the name you want is taken, then invent another name! Don't find alternative ways to write the same thing for that WILL cause confusion and WILL look ugly.

It is not even true. "vars" is not a reserved Perl word. There is a module called vars, but use is not the context. The context is a sub/method name, and you can without any trouble call that &vars:

use strict;
use warnings;

sub vars { 1 + 1 }
print vars;
print main->vars;

I use Params::Validate to normalize the keys, allowing but not requiring the prefixed minus.

The only reason a minus is needed or wanted is wanting to allow a combination of positional and named arguments. Allowing a minus is nice for people who insist on consistent style (but those people should prepare for re-coding CPAN entirely), but IMnsHO it's a waste of CPU cycles to look for them.