Mailing-List: contact dev-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.apache.org
Subject: Re: About declaring the field and property with same name
To: dev@groovy.apache.org
References: <1499474014684-5742010.post@n5.nabble.com>
 <1499874498283-5742072.post@n5.nabble.com>
From: Jochen Theodorou <blackdrag@gmx.org>
Message-ID: <498dd031-079a-9f4c-4ef3-c7b203423275@gmx.org>
Date: Wed, 12 Jul 2017 18:11:51 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <1499874498283-5742072.post@n5.nabble.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Wed, 12 Jul 2017 16:12:07 -0000


On 12.07.2017 17:48, Daniel Sun wrote:
> Hi all,
>
>         If no one is opposed to deprecating the weird feature, I'll modify
> the two tests at the weekend(shouldCompile -> shouldNotCompile):
>
> https://github.com/apache/groovy/blob/master/src/test/gls/scope/MultipleDefinitionOfSameVariableTest.groovy#L110
>
> https://github.com/apache/groovy/blob/master/src/test/gls/scope/MultipleDefinitionOfSameVariableTest.groovy#L119
>

sorry, but veto.

class X {
   String foo
   private foo
}

declares for example a get/setFoo for String, while the backing field is 
Object. The field also allows you to use additional modifiers like 
volatile for example.

bye Jochen