On Thu, Feb 19, 2004 at 10:02:55AM -0800, Scott wrote:
>
> Anyway, I very much realize the naming isn't entirely up to me but
> personally I would prefer a short, single word name that denotes the
> activity of the method as opposed to something that doesn't seem proper
> in the context of the kernel, simply inherited from some programming
> language I've never used. But thats just my personal preference.
I suggested $kernel->do("event") on IRC. While Scott (hi, you) didn't
like it, it's a viable option.
Possibilities for call-on-current-ssesion:
$kernel->invoke("event"); # ambiguous, Scott's favorite
$kernel->do("event"); # ambiguous, shorter than call, but Perl
$kernel->gosub("event"); # more specific, comes from BASIC, silly
$kernel->call_me("event"); # specific, ugly
$kernel->me_call("event"); # specific, ugly, follows noun_verb naming
... plus future suggestions. I'm inclined to say invoke() because it's
the least offensive of the options so far. It's neither silly, nor
particularly ugly, nor does it conflict with a Perl built-in command.
This thread seems to be winding down. If there are no serious
objections (by which I mean ones that include alternative suggestions),
I'll apply Scott's patch, and invoke() will be it.
How long is "long enough" to wait before closing a decided design
thread? My best guess is a week.
--
Rocco Caputo - [EMAIL PROTECTED] - http://poe.perl.org/
