[jboss-jira] [JBoss JIRA] Commented: (JBRULES-269) Parser to be stricter with newlines
Michael Neale (JIRA)
jira-events at jboss.com
Sun Nov 12 16:03:41 EST 2006
[ http://jira.jboss.com/jira/browse/JBRULES-269?page=comments#action_12346744 ]
Michael Neale commented on JBRULES-269:
---------------------------------------
ha ! yes I like python, as long as we don't start requiring indentation ;)
we may have some other ways to avoid so many keyword collisions (using semantic predicates for working out keywords rather then hard coded tokens for the lexer).
> Parser to be stricter with newlines
> -----------------------------------
>
> Key: JBRULES-269
> URL: http://jira.jboss.com/jira/browse/JBRULES-269
> Project: JBoss Rules
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Drl Parser/Builder
> Affects Versions: 3.0-rc2
> Reporter: Michael Neale
> Assigned To: Michael Neale
> Fix For: 3.1-m3
>
>
> Given that we are not going down the route of
> when {
> }
> style brackets, we will need to be stricter about newlines.
> In otherwords, newlines are required I believe in the following scenarious:
> before a when,
> after a when before the LHS
> before a then
> after a then before then RHS
> before an end (at the end of the rule).
> when,then, end - should all appear on a line by themselves.
> Optionally (perhaps?) rule should always be at the start of a newline.
> on a similar note, should rule and end be at the start of a newline? (don't really want to have to enforce column positions - but it is kind of needed).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list