Re: Groov 3.0 - nested code blocks - block/eval

I’m against breaking changes and changing core concepts for so little gain. Groovy has (x) to make x an expression. We could make that lexically scoped. Dierk sent from:mobile > Am 21.03.2018 um 01:53 schrieb MG : > > Hi Daniel, > >> On 21.03.2018 01:33, Daniel Sun

Re: Groov 3.0 - nested code blocks - block/eval

Hi Daniel, On 21.03.2018 01:33, Daniel Sun wrote: Parrot is smart enough to distinguish closure and code block, so `block` is not necessary. Under http://groovy-lang.org/releasenotes/groovy-3.0.html it says: "Be aware though that in Groovy having a code block looking structure after

Re: Groov 3.0 - nested code blocks - block/eval

Hi mg, Parrot is smart enough to distinguish closure and code block, so `block` is not necessary. BTW, new keywords may break existing code ;) As for `eval`, we can use `{ /* do something here */ }()` instead, e.g. `{ 'abc' }()` P.S. I am open to any proposal for grammar ;-) Cheers,