You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@groovy.apache.org by "Leifur Halldor Asgeirsson (JIRA)" <ji...@apache.org> on 2016/08/31 15:01:20 UTC

[jira] [Commented] (GROOVY-3010) fix private field visibility

    [ https://issues.apache.org/jira/browse/GROOVY-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15452463#comment-15452463 ] 

Leifur Halldor Asgeirsson commented on GROOVY-3010:
---------------------------------------------------

I was a little confused today after importing a Java class in Groovy and finding that the private access modifier seemed to be ignored. I think it would be helpful to include some kind of warning or explanation about this behavior in the docs at groovy-lang.org; I understand that this is considered subject to change, but that doesn't prevent documenting this behavior as long as it's made clear that it's subject to change.

> fix private field visibility
> ----------------------------
>
>                 Key: GROOVY-3010
>                 URL: https://issues.apache.org/jira/browse/GROOVY-3010
>             Project: Groovy
>          Issue Type: Task
>          Components: groovy-runtime
>            Reporter: Jochen Theodorou
>             Fix For: 3.0
>
>         Attachments: privateInJsUseWrapMethodExample.js
>
>
> this task collects all the issues related to a privae field being visible, when it should not be visible



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)