[
https://issues.apache.org/jira/browse/GROOVY-7578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731956#comment-14731956
]
Paul King edited comment on GROOVY-7578 at 9/5/15 12:18 PM:
------------------------------------------------------------
The image is definitely meant to be a summary of what goes on. There is scope
for adding more detail but it might then become harder to get the overall
picture. Also, when you start looking at the trickier areas such as
inheritance, I think there might be some edge cases with slight differences
when you look at ExpandoMetaClass vs categories vs ExtensionMethods. The
current plan was to make simplifications for MOP2 that would potentially allow
us to produce a more comprehensive picture that was still readable and
hopefully with edge case anomalies removed or greatly reduced.
When writing ReGinA we covered in reasonable detail all the parts of the
behavior that we thought were stable and commonly used. I;m not sure whether
that would help you. Some less commonly used parts which we thought might
change with MOP2 we tried to just summarize. I'll have a look at the SO
question if I get time but the next few weeks are pretty hectic.
was (Author: paulk):
The image is definitely meant to be a summary of what goes on. There is scope
for adding more detail but it might then become harder to get the overall
picture. Also, when you start looking at the trickier areas such as
inheritance, I think there might be some edge cases with slight differences
when you look at ExpandoMetaClass vs categories vs ExtensionMethods. The
current plan was to make simplifications for MOP2 that would potentially allow
us to produce a more comprehensive picture that was still readable and
hopefully with edge case anomalies removed or greatly reduced.
> Image present for metaprogramming is incorrect
> ----------------------------------------------
>
> Key: GROOVY-7578
> URL: https://issues.apache.org/jira/browse/GROOVY-7578
> Project: Groovy
> Issue Type: Documentation
> Reporter: Aseem Bansal
>
> I am reading groovy metaprogramming documentation and saw that the image
> present is wrong. I mean there is an image present but the flow is wrong.
> It has a block "Method exists in MetaClass or Class" two times. One after
> GroovyInterceptable and other after the first "Method exists in MetaClass or
> Class" .
> I tried a simple program and as per this I believe the first block should
> have class only and second block should have MetaClass only
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
