Re^5: Easily catalog subroutines with a synopsis comment

The module name is EEBL::Game, and it is called (eventually) via the public API of playball. I would hope that when I reference my API's within the context of a specific module that they make sense.

I wonder if writers and linguistics would make a better programmers than a mathematicians? The ability to express yourself clearly in your code, to often seems to be a secondary concern for too many programmers.

Comment on Re^5: Easily catalog subroutines with a synopsis comment

Replies are listed 'Best First'.
Re^6: Easily catalog subroutines with a synopsis comment by BrowserUk (Patriarch) on Apr 20, 2008 at 00:58 UTC
It just struck me that in the context of a module called playball, prefixing all the api or method names with `__playball_...` is somewhat redundant. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply] [d/l]
Re^7: Easily catalog subroutines with a synopsis comment by Herkum (Parson) on Apr 20, 2008 at 05:21 UTC
Sorry, maybe I was not clear, the module is EEBL::Game, the API is playball so, `my $game = EEBL::Game->new(); $game->playball;` [download] There are other APIs related to the Game that have no reference to 'playball', to keep it organized(and from me going insane), I prefix '__' to appropriate internal subs.	[reply] [d/l]