On 2004-11-03, Michael G Schwern <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 03, 2004 at 12:19:08AM +0100, Abigail wrote:
>> While I won't deny 'err' may be used in many existing programs, I doubt
>> it's used more than 'lock' was before 'lock' was introduced as a keyword.
I wouldn't be so sure. I imagine I a lot more people have to deal with
'errors' than they do with 'locks'. I'm one of those people has
production code with a subroutine named 'err' it, and would like to
avoid the hassle of changing that in a number of places.
> Difference between lock() and err() is this.
>
> $ perl5.6.1 -wle 'sub lock { "foo" } print lock'
> foo
> $ bleadperl -wle 'sub lock { "foo" } print lock'
> foo
> $ bleadperl -wle 'sub err { "foo" } print err'
> Ambiguous call resolved as CORE::err(), qualify as such or use & at -e line 1.
> syntax error at -e line 1, at EOF
> Execution of -e aborted due to compilation errors.
This seems like an important difference. It would be nice if my 'err'
routines could keep working, like custom 'lock' routines appeared to.
Mark
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark Stosberg Principal Developer
[EMAIL PROTECTED] Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .
