Re^5: Easy dispatch tables. (can() be even easier)

I agree the second and third are more opaque than your snippets, but that's because there's no function that hides the guts - you could define a Foo::_callables() and then it wouldn't look any more intimidating than your examples (of course that's 90% of what you do, anyway).

But really, if I need to call a series of functions, I'd put them in a hash or array. And I really think the UNIVERSAL::can example is the simplest solution for that case.

Which, silly me, can of course be written

Foo->$bar($baz) if Foo->can($bar);
[download]

and then I think there's really no debate anymore over whether that's simple.

Makeshifts last the longest.

Comment on Re^5: Easy dispatch tables. (can() be even easier) Download Code

Replies are listed 'Best First'.
Re: Re^5: Easy dispatch tables. by jryan (Vicar) on Apr 03, 2003 at 21:59 UTC
I agree, that's pretty simple. However, you still don't have all of the advantages of working with a hash, such as `keys`, `values`, and `tie`. And sure, you could define your own function do to that, but why would you want to if there is a module that does it for you? You don't write your own CGI parsing routines, do you?	[reply] [d/l] [select]
Re^7: Easy dispatch tables. (see previous) by Aristotle (Chancellor) on Apr 04, 2003 at 15:25 UTC
True, but that's why I gave my last two examples. Makeshifts last the longest.	[reply]