groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Laforge <glafo...@gmail.com>
Subject Re: Groovy 2.5.4 planning
Date Fri, 02 Nov 2018 09:04:11 GMT
I was also thinking of a Boolean in a constructor.

Le ven. 2 nov. 2018 à 07:23, Paul King <paulk@asert.com.au> 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 like use different GProperty
> instances in different contexts with different security contexts.
>
> Given use of GProperties is totally opt-in, I am wondering if a switch is
> needed but I am open to others thoughts on this topic. If a switch is
> needed, my suggestion would be different constructors with some boolean
> flags to indicate what features are enabled for a particular instance.
>
> Cheers, Paul.
>
>
> On Fri, Nov 2, 2018 at 1:15 PM Daniel Sun <realbluesun@hotmail.com> wrote:
>
>> Hi Andres,
>>
>>       > if GProperties is added to core I’d suggest to set that flag to
>> false as default.
>>       Agreed :)
>>
>>       > Additionally, couldn’t this behavior be added to ConfigSlurper?
>>       As you can see, `GProperties` is a subclass of `Properties`, I
>> recommend groovy users to use the enhanced `Properties` by
>> default(`GProperties` to `Properties` is similar with `GString` to
>> `String`), which can handle properties smartly and handle input
>> stream/reader properly
>>
>> Cheers,
>> Daniel.Sun
>>
>>
>>
>> --
>> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>>
>

Mime
View raw message