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 Ovchinniko
This:
> Example:
> package void foo() {}
—
Daniil Ovchinnikov
JetBrains
jetbrains.com
“Drive to develop"
> On 14 Dec 2017, at 01:37, Nathan Harvey wrote:
>
> I meant that the @PackageScope annotation made code look somewhat unreadable,
> and that the "package" keyword would be an ideal solut
I meant that the @PackageScope annotation made code look somewhat unreadable,
and that the "package" keyword would be an ideal solution.
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
"this" in this case being bound to ?-)(i.e. what do you mean by "this" - having
a package keyword or an annotation ?)
Ursprüngliche Nachricht Von: Daniil Ovchinnikov
Datum: 13.12.17 23:14 (GMT+01:00) An:
dev@groovy.apache.org Betreff: Re: Package specific syntax
This is the
This is the best way from IDE perspective.
—
Daniil Ovchinnikov
JetBrains
jetbrains.com
“Drive to develop"
> On 14 Dec 2017, at 01:03, Nathan Harvey wrote:
>
> In Java, methods and fields use package scope by default. In Groovy, they
> use public. In order to make something package scope, you
Extension methods are a very powerful feature in Groovy, but they are also
difficult (and somewhat tedious) to use because they require being in
another project. I believe one reason for this limitation is the syntax of
extension methods, which are exactly the same as other methods, and so they
nee
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,
So is it still possible to produce the groovy-all.jar and
groovy-all-sources.jar from the SDK zip?
Note that I'm still not done with fixing. Things are in a much better shape
now, but the build is still doing very bad things. Typically this:
```
task docProjectVersionInfo(type: Copy) {
destinationDir =
file("${project(':groovy-docgenerator').sourceSets.main.java.outputDir}")
into('META
Fixed, thanks for reporting.
> In addition, Groovy Version can not be shown properly(Groovy Version:
> #ImplementationVersion#):
>
> C:\Users\Daniel>groovy -v
> Groovy Version: #ImplementationVersion# JVM: 1.8.0_121 Vendor: Oracle
> Corporation OS: Windows 10
>
>
> Cheers,
> Daniel.Sun
>
>
>
>
>
10 matches
Mail list logo
