[jboss-jira] [JBoss JIRA] (JBRULES-3363) Add support to inline constraints on multi-function accumulate

[Edson Tirelli (JIRA)]

     [ https://issues.jboss.org/browse/JBRULES-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Edson Tirelli closed JBRULES-3363.
----------------------------------


    
> Add support to inline constraints on multi-function accumulate
> --------------------------------------------------------------
>
>                 Key: JBRULES-3363
>                 URL: https://issues.jboss.org/browse/JBRULES-3363
>             Project: Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-compiler, drools-core
>    Affects Versions: 5.4.0.Beta1
>            Reporter: Edson Tirelli
>            Assignee: Edson Tirelli
>             Fix For: 5.4.0.Final, 5.5.0.Beta1
>
>
> FROM MARK:
> ===========
> Edson,
> While I don't want to change to acc/for keyword quite yet, until we are sure what drastic changes we want to make to syntax. I think we can evolve accumulate()
> 1) make the first ", " optionall [,;]. Where the documented new separate is ";"
> 2) functions are still "," separated
> 3) allow an optional second ";" after this boolean expression, an eval without the eval wrapper.
> 3. can be done now with a separate eval(....) after the accumulate. But I think good to encapsulate the intent of the guard within the accumulate itself, it's also another opportunity to remove the "eval" keyword for a common use case. For now we'll just rewrite the accumulate to place an eval() CE after the acc. It's a small win, which I think will make the DRL look nicer, especially for CEP use cases.
> ============
> FROM EDSON:
> ============
>  Mark,
>    (1) and (2) are ok. Regarding (3), we can embed the expression in the accumulate node itself. No need for a separate node. And if we use ; as the separator, we don't need the eval() keyword.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira