groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From MG <mg...@arscreat.com>
Subject Re: Package specific syntax
Date Thu, 14 Dec 2017 01:11:06 GMT
Why is a keyword better than an annotation from an IDE developer's 
perspective (considering Groovy already has tons of annotations which 
more complex semantics than @PackageScope) ?


On 13.12.2017 23:14, Daniil Ovchinnikov wrote:
> This is the best way from IDE perspective.
>
> —
>
> Daniil Ovchinnikov
> JetBrains
> jetbrains.com <http://jetbrains.com>
> “Drive to develop"
>
>> On 14 Dec 2017, at 01:03, Nathan Harvey <nathanwharvey@gmail.com 
>> <mailto:nathanwharvey@gmail.com>> wrote:
>>
>> In Java,  methods and fields use package scope by default. In Groovy, 
>> they
>> use public. In order to make something package scope, you have to use the
>> @PackageScope annotation. This makes code look a bit messy but also 
>> doesn't
>> seem very intuitive. What if the "package" keyword was able to be 
>> applied,
>> in exactly the same way as "public" and "private" are?
>>
>> Example:
>> package void foo() {}
>>
>>
>>
>> --
>> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>


Mime
View raw message