Re: Why callbacks?

Callbacks are great for injecting behaviour into something - ruby calls them mixins.

Instead of having variables referenced within the function, outward, to something lexically scoped or globally is really weird. I would expect the callback retaining the data and you querying it for the result. Hrm..

Comment on Re: Why callbacks?

Replies are listed 'Best First'.
Re^2: Why callbacks? by Joost (Canon) on Mar 30, 2007 at 17:56 UTC
Ruby mixins aren't really callbacks - they insert new methods into classes / objects. Some of those methods might be used as callbacks, but a clearer example of callbacks in ruby are code blocks/Procs "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re^3: Why callbacks? by friedo (Prior) on Mar 31, 2007 at 01:19 UTC
You can do mixins in Perl as well, by using Exporter to import methods into an OO class. CGI::Application uses this technique to add methods via plugins.	[reply]
Re^3: Why callbacks? by exussum0 (Vicar) on Mar 30, 2007 at 21:03 UTC
Right right, was using the wrong terminology for what i meant. tnx.	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.
A reply falls below the community's threshold of quality. You may see it by logging in.


more useful options
	PerlMonks