[
https://issues.apache.org/jira/browse/GROOVY-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980576#comment-15980576
]
ASF GitHub Bot commented on GROOVY-7579:
----------------------------------------
GitHub user jwagenleitner opened a pull request:
https://github.com/apache/groovy/pull/528
GROOVY-7579: Improve docs for invokeMethod
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jwagenleitner/groovy groovy7579
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/groovy/pull/528.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #528
----
commit 79cd42d410310f6d2ea34a13e78d621dc2e658a9
Author: John Wagenleitner <[email protected]>
Date: 2017-04-23T23:06:13Z
GROOVY-7579: Improve docs for invokeMethod
----
> 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
>
> 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)
