[jboss-jira] [JBoss JIRA] Issue Comment Edited: (JBRULES-3147) Regression: all uppercase field reference results in compile error
[
https://issues.jboss.org/browse/JBRULES-3147?page=com.atlassian.jira.plug...
]
Wolfgang Laun edited comment on JBRULES-3147 at 7/27/11 1:47 AM:
-----------------------------------------------------------------
Report by Tom E. Murphy
this does not compile in 5.2.0 (OK in 5.0.1):
Foo( MICompanyMarketClassification in (“2”, “3”) )
this works in 5.2. but did not in 5.0.1:
Foo( mICompanyMarketClassification in ... )
this works in 5.2:
Foo( FHAMaxBaseMortgageWithToleranceAmt < (...) )
was (Author: laune):
Report by
this does not compile in 5.2.0 (OK in 5.0.1):
Foo( MICompanyMarketClassification in (“2”, “3”) )
this works in 5.2. but did not in 5.0.1:
Foo( mICompanyMarketClassification in ... )
this works in 5.2:
Foo( FHAMaxBaseMortgageWithToleranceAmt < (...) )
Regression: all uppercase field reference results in compile error
------------------------------------------------------------------
Key: JBRULES-3147
URL: https://issues.jboss.org/browse/JBRULES-3147
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Fix For: 5.2.1.Final
Consider the following ways of writing getters, setters and pattern field names
element xetter field 5.1.1 5.3.0
=============================================
state xetstate state OK OK
state xetState state OK OK
staTe xetStaTe staTe OK OK
state xetSTATE STATE OK ERR
The last variation is a regression from 5.1.1. It is not so absurd - if the field is
designated with an acronym (XML,...) this would be the natural way to write xetters and
the pattern field.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira