Re: About the enhanced version of `Properties`, i.e. `GProperties`

2018-11-02 Thread Daniel.Sun
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

Re: About the enhanced version of `Properties`, i.e. `GProperties`

2018-11-02 Thread Daniil Ovchinnikov
Did you consider using different file extension? — Daniil Ovchinnikov JetBrains > On 2 Nov 2018, at 18:39, Daniel.Sun wrote: > > I've added some doc to show the usage: > >

Re: About the enhanced version of `Properties`, i.e. `GProperties`

2018-11-02 Thread Daniel.Sun
I've added some doc to show the usage: https://github.com/apache/groovy/blob/3775edeabde19eb5229e840ec2ffc1dcf90634db/src/main/groovy/groovy/util/GProperties.groovy Cheers, Daniel.Sun - Daniel Sun Apache Groovy committer Blog: http://blog.sunlan.me Twitter: @daniel_sun -- Sent

Re: About refining regex literal syntax

2018-11-02 Thread MG
Am 22.10.2018 um 22:34 schrieb Guillaume Laforge: Damn, MG will tell me again I'm reacting negatively to Daniel's ideas but... :-) No, no - it's not a knee jerk reaction. In this case I see both points, and am torn on what I would prefer... (Generally speaking, while having a "regex

Re: About simplifying the switch for runtime groovydoc

2018-11-02 Thread MG
Agree with Guillaume here: In my (bad) experience, 15 Facebook friends is all it takes to swing nearly any poll in your favour and get a landslide victory. Am 24.10.2018 um 16:12 schrieb Guillaume Laforge: Not necessarily. Discussions are better, leading towards a consensus. Polls can have

Re: About the enhanced version of `Properties`, i.e. `GProperties`

2018-11-02 Thread Daniel.Sun
Here are some tests to show its usage: https://github.com/apache/groovy/blob/96e94cf80ca4fc8449231e2f92508bca516bce87/src/test/groovy/util/GPropertiesTest.groovy and here are the relevant properties files: 1,

Re: About the enhanced version of `Properties`, i.e. `GProperties`

2018-11-02 Thread Milles, Eric (TR Tech, Content & Ops)
Can there be an example of its use shown before it is automatically merged into master/3.0? Even the pull request and javadoc of the class do not describe its usage. How can someone evaluate it this way and what are the alternatives if this does not exist?

Re: Groovy 2.5.4 planning

2018-11-02 Thread Daniel Sun
Gotcha. The `GProperties` will be included in 3.0.0. Cheers, Daniel.Sun -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: Groovy 2.5.4 planning

2018-11-02 Thread Guillaume Laforge
Agreed, we normally don't add new features in bug fix releases, but only in main releases. On Fri, Nov 2, 2018 at 10:07 AM Cédric Champeau wrote: > -1 to including GProperties in a bugfix release. There's apparently > discussion about the implication of doing this, and a bugfix release is not >

Re: Groovy 2.5.4 planning

2018-11-02 Thread Guillaume Laforge
I was also thinking of a Boolean in a constructor. Le ven. 2 nov. 2018 à 07:23, Paul King a écrit : > While I think security is very important to consider, I am unsure whether > the switch is the way to go. Such switches are global in nature and that > means you can't as easily as you might

Re: Groovy 2.5.4 planning

2018-11-02 Thread Paul King
While I think security is very important to consider, I am unsure whether the switch is the way to go. Such switches are global in nature and that means you can't as easily as you might like use different GProperty instances in different contexts with different security contexts. Given use of