groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cédric Champeau <cedric.champ...@gmail.com>
Subject Re: About the enhanced version of `Properties`, i.e. `GProperties`
Date Tue, 06 Nov 2018 11:02:38 GMT
+1 to using a different file extension for gproperties

Le mar. 6 nov. 2018 à 11:32, Daniil Ovchinnikov <
daniil.ovchinnikov@jetbrains.com> a écrit :

>  we can not replace Properties in existing groovy
> code easily because we have to change the file extension
>
>
> Exactly this.
>
> Also please consider tooling. We already have support for .properties in
> IntelliJ based on file extension.
> If .properties would be used for GProperties, then user should go in
> settings and change mapping for all .properties files to be handled as
> GProperties.
> And what if some file is actually Properties one and another is
> GProperties? It’s just confusing.
>
> Imagine you create a new language (say Groovy) which is syntax-compatible
> with Java and you use its default extension (.java), because why not,
> otherwise you should change file extension of your existing .java files.
>
> —
>
> Daniil Ovchinnikov
> JetBrains
>
> On 3 Nov 2018, at 07:11, Daniel.Sun <sunlan@apache.org> wrote:
>
> No. GProperties to Properties is similar with GString to String,
> GProperties
> is much more powerful than Properties, so I recommend groovy users use
> GProperties where Properties is used. If GProperties only process the file
> with new file extension, we can not replace Properties in existing groovy
> code easily because we have to change the file extension.
>
> Cheers,
> Daniel.Sun
>
>
>
>
> -----
> Daniel Sun
> Apache Groovy committer
> Blog: http://blog.sunlan.me
> Twitter: @daniel_sun
>
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>
>
>

Mime
View raw message