[jira] [Updated] (GROOVY-2768) Add sender of method calls as a parameter to the methods of MetaClass

2022-01-02 Thread Eric Milles (Jira)


 [ 
https://issues.apache.org/jira/browse/GROOVY-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Milles updated GROOVY-2768:

Fix Version/s: (was: 4.x)

> Add sender of method calls as a parameter to the methods of MetaClass
> -
>
> Key: GROOVY-2768
> URL: https://issues.apache.org/jira/browse/GROOVY-2768
> Project: Groovy
>  Issue Type: Improvement
>  Components: groovy-runtime
>Reporter: Arvid Heise
>Priority: Minor
>
> MetaClass extends the MOP interface with methods which have a senderClass as 
> their first parameter. Unfortunately, the param does not refer to the sender 
> of the original method call but is in most cases identical to the receiver's 
> class.
> Knowing the sender of a method call would allow interesting reflective 
> program structures like subjective programming with a three-dimensional 
> message dispatch. A method can not only be overwritten by the receiver with 
> polymorphism but also by the sender. Refer to 
> http://citeseer.ist.psu.edu/smith96simple.html for more details.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Updated] (GROOVY-2768) Add sender of method calls as a parameter to the methods of MetaClass

2020-01-27 Thread Paul King (Jira)


 [ 
https://issues.apache.org/jira/browse/GROOVY-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul King updated GROOVY-2768:
--
Fix Version/s: (was: 3.x)
   4.x

> Add sender of method calls as a parameter to the methods of MetaClass
> -
>
> Key: GROOVY-2768
> URL: https://issues.apache.org/jira/browse/GROOVY-2768
> Project: Groovy
>  Issue Type: Improvement
>  Components: groovy-runtime
>Reporter: Arvid Heise
>Priority: Minor
> Fix For: 4.x
>
>
> MetaClass extends the MOP interface with methods which have a senderClass as 
> their first parameter. Unfortunately, the param does not refer to the sender 
> of the original method call but is in most cases identical to the receiver's 
> class.
> Knowing the sender of a method call would allow interesting reflective 
> program structures like subjective programming with a three-dimensional 
> message dispatch. A method can not only be overwritten by the receiver with 
> polymorphism but also by the sender. Refer to 
> http://citeseer.ist.psu.edu/smith96simple.html for more details.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)