Revision as of 16:53, 22 August 2005 edit CarlHewitt (talk \| contribs) 5,700 edits →Implementation, actors, concurrency ← Previous edit		Revision as of 10:14, 30 October 2005 edit undo 61.59.251.140 (talk) No edit summary Next edit →
Line 1: ==Closures in Perl== In perl at least, a closure doesn't have to be a function definition. It's more or less anything between a pair of braces, that serves as it's own variable scope. In Damian Conway's ''Object Oriented Perl'', I believe he uses closures to implement the private variables of an object, so it might be misleading to say that the closure itself is an object or acts like one. In any case, something needs to be said about scope here. [[user:Wesley\|Wesley]] How could one use a closure that's not a function definition?

Talk:Closure (computer programming): Difference between revisions