You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@groovy.apache.org by GitBox <gi...@apache.org> on 2020/08/07 13:24:46 UTC

[GitHub] [groovy] eric-milles commented on pull request #1342: GROOVY-9675: There should be a mechanism to disable individual macro …

eric-milles commented on pull request #1342:
URL: https://github.com/apache/groovy/pull/1342#issuecomment-670514899


   Is there ever a reason to set one of these properties to true?  Instead how about one property that is set the the name(s) of the disabled macros or extensions?  Like, `-Dgroovy.macro.disable=*` or `-Dgroovy.macro.disable=foo,bar` or a pattern that could be compiled once and matched against the names.
   
   Will it be possible to disable macros or extensions using compiler configuration?  Or is this just a system property mechanism?  IMO there are too many special system property controls/switches.
   
   If I want to disable just one instance of `each` or `getAt` (for example) is that possible or must it be all or none?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org