You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (JIRA)" <ji...@apache.org> on 2017/05/02 02:04:18 UTC

[jira] [Closed] (GROOVY-7579) Improve docs for invokeMethod

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

Paul King closed GROOVY-7579.
-----------------------------

> Improve docs for invokeMethod
> -----------------------------
>
>                 Key: GROOVY-7579
>                 URL: https://issues.apache.org/jira/browse/GROOVY-7579
>             Project: Groovy
>          Issue Type: Documentation
>          Components: Documentation
>    Affects Versions: 2.4.5
>            Reporter: Aseem Bansal
>            Assignee: John Wagenleitner
>             Fix For: 2.4.11
>
>
> I was reading meta programming documentation when I noticed that "this method is called when the method you called is not present on a Groovy object"
> As per the diagram it is incorrect. It is invoked when methodMissing is not present. This statement is as per the diagram.
> Also as per the answer at this is not an appropriate example  http://stackoverflow.com/questions/19220370/what-is-the-difference-between-invokemethod-and-methodmissing
> Saying this because the answer by blackdrag (who I understand is a core committer to groovy) says that methodMissing should be used instead. 
> Also the same page mentions "overhead of invokeMethod". It would be nic e to have a better explanation in the section of invokeMethod itself.
> I am not knowledgeable about this so cannot suggest what can be added. But it would be better to have the explanation in the official docs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)