[
https://issues.apache.org/jira/browse/GROOVY-8474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357132#comment-16357132
]
Jochen Theodorou commented on GROOVY-8474:
------------------------------------------
[~paulk] you are right, it only got moved
[~daniel_sun] thanks for the fix, but you may have changed semantics. If we
prefer the getter for a super call, then why should we prefer the field in case
of a setter? I was already in this area before with the bug I tried to fix
around xmas, and noticed this for me strange behavior back then. I do prefer
your way of course. But I do not think it aligns with what we have. So changing
the order in your helper method would fix this.... and we really should define
this better... and maybe redefine this for Groovy 3
> 'Unexpected super property set for:' when accessing super class property via
> super.propertyName
> -----------------------------------------------------------------------------------------------
>
> Key: GROOVY-8474
> URL: https://issues.apache.org/jira/browse/GROOVY-8474
> Project: Groovy
> Issue Type: Bug
> Affects Versions: 2.4.13
> Environment: Mac OS X, JDK 8
> Reporter: zhb
> Assignee: Daniel Sun
> Priority: Critical
>
>
> {{class T {}}
> {{ String group}}
> {{}}}
> {{class S extends T {}}
> {{ S() {}}
> {{ super.group = ''}}
> }
> {{}}}
>
> BUG! exception in phase 'class generation' in source unit
> 'ideaGroovyConsole.groovy' Unexpected super property set for:super.group
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
