Re: is it ok to name object methods after core functions?

in reply to is it ok to name object methods after core functions?

Also you should keep in mind that Perl::Critic will complain about builtin function overwrites. Choosing different names spares you these automatic review comments.

print+qq(\L@{ref\&@}@{'@'x7^'!#2/"!4'})

Comment on Re: is it ok to name object methods after core functions?

Replies are listed 'Best First'.
Re^2: is it ok to name object methods after core functions? by adrianh (Chancellor) on Aug 03, 2007 at 12:36 UTC
Also you should keep in mind that Perl::Critic will complain about builtin function overwrites It's "may complain" not "will complain". P::C is configurable in all things. I love P::C, but changing code just to make a comment disappear isn't what it's about. It highlights things that may be problems. Change them if it makes your code better. If <code>$door->open</open> is more intention revealing than the alternatives leave it alone.	[reply]

Replies are listed 'Best First'.

Re^2: is it ok to name object methods after core functions?
by adrianh (Chancellor) on Aug 03, 2007 at 12:36 UTC

Also you should keep in mind that Perl::Critic will complain about builtin function overwrites

It's "may complain" not "will complain". P::C is configurable in all things.

I love P::C, but changing code just to make a comment disappear isn't what it's about. It highlights things that may be problems. Change them if it makes your code better. If <code>$door->open</open> is more intention revealing than the alternatives leave it alone.

[reply]

In Section Seekers of Perl Wisdom