[GROOVY-764] closures

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0
• Assignee: Jochen Theodorou
• Reporter: Jochen Theodorou
• Created: 04/Mar/05 11:04
• Updated: 02/Nov/07 06:58
• Resolved: 02/Nov/07 06:58

Description

This is a meta task. This means this task should not be closed nor is it for error reporting, wishes or improvements. If you have any of them related to this task please fill a normal issue and link it to this.

Issue Links

• depends upon: GROOVY-584 Exception passing array into Closure
• depends upon: GROOVY-265 The delegate is ignored when resolving names in a closure in a script
• depends upon: GROOVY-266 an inner closure doesn't use the outer closures delegate to resolve names
• depends upon: GROOVY-279 closures don't find variables in a delegate if the variable written to before it's read
• depends upon: GROOVY-384 The inner class representing a closure has a bad constructor
• depends upon: GROOVY-511 The delegate of an eclosing closure is not being used to resolve references
• depends upon: GROOVY-534 Nested closures - variable scope problem
• depends upon: GROOVY-613 global properties referenced from closure that are declared later cause early NullPointer
• depends upon: GROOVY-634 variable assignment within nested closures doesn't work
• depends upon: GROOVY-886 each(){} throws NPE when called on a Java Object[], that contains String[]'s with null entries
• depends upon: GROOVY-888 Object[] vs int[]
• depends upon: GROOVY-918 Cannot set outside variables from within nested closures
• depends upon: GROOVY-723 MethodClosure doesn't support variable arguments method
• depends upon: GROOVY-319 Support for rendevous symantics
• depends upon: GROOVY-298 have a transactional closure and/or some kind of retry/timeout closure method