Re^2: Yet another set of Perl best practices

No, I really mean the subs/methods, not their names.

IMO subs/methods should do something specific, clear and easy to explain (at least, once you have a good vocabulary for the problem space at hand).

Though, if you have problems naming your methods, it is probably a good indication that you are not doing that right.

Maybe meaningful is not the right word here...

Comment on Re^2: Yet another set of Perl best practices

Replies are listed 'Best First'.
Re^3: Yet another set of Perl best practices by Anonymous Monk on Aug 24, 2012 at 13:55 UTC
Maybe meaningful is not the right word here... I think meaningful is definitely the wrong word, hey, everything has meaning :) IMO subs/methods should do something specific, clear and easy to explain Like a purpose? Dang, thats just meaning! This is hard! This is a problem with your list, you know what you mean by it, but didn't write that down :) Hmm, A good subroutine is readable and has a well-defined interface, strong internal cohesion, and loose external coupling --- is the word Modular?	[reply]

Replies are listed 'Best First'.

Maybe meaningful is not the right word here...

I think meaningful is definitely the wrong word, hey, everything has meaning :)

IMO subs/methods should do something specific, clear and easy to explain

Like a purpose?

Dang, thats just meaning!

This is hard!

This is a problem with your list, you know what you mean by it, but didn't write that down :)