Reading the grammar in the CIM-SPL spec, it appears that f().g() is not
allowed, although f(g()) is. This is very serious problem in my mind and
should be addressed by either updating the spec and/or adding extensions
in Imperius. Thoughts?
David Wood
Policy Technologies Group
IBM TJ Watson Research Center
daw...@us.ibm.com
914-784-5123 (office), 914-396-6515 (mobile)
From:
Xiping Wang/Watson/i...@ibmus
To:
imperius-dev@incubator.apache.org
Date:
03/11/2009 03:03 PM
Subject:
Re: [jira] Created: (IMPERIUS-26) Argument parsing for reference to
toString() is wrong
I believe that the Imperius parser does not support certain operations as
Neeraj mentioned before. It is a good idea for us to document those
unsupported operations.
Xiping
"David Wood (JIRA)" <j...@apache.org>
"David Wood (JIRA)" <j...@apache.org>
03/11/2009 02:48 PM
Please respond to
imperius-dev@incubator.apache.org
To
imperius-dev@incubator.apache.org
cc
Subject
[jira] Created: (IMPERIUS-26) Argument parsing for reference to toString()
is wrong
Argument parsing for reference to toString() is wrong
-----------------------------------------------------
Key: IMPERIUS-26
URL: https://issues.apache.org/jira/browse/IMPERIUS-26
Project: Imperius
Issue Type: Bug
Reporter: David Wood
Assignee: Bill Stoddard
With the following policy:
Import Class java.util.Properties:list1;
Strategy Execute_All_Applicable;
Policy
{
Condition
{
list1.get("Foo").toString() == "something"
}
Decision
{
list1.toString()
}
}:1;
I get
Number of Formal and passed parameters don't match for method toString
This code used throw an exception (not sure why it's not now). This is
produced based on a problem we are seeing with some other classes which
DOES throw the exception. In looking into this a bit, it looks as if the
"Foo" argument to the previous method is being passed to toString().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
