You are viewing a plain text version of this content. The canonical link for it is here.
Posted to imperius-dev@incubator.apache.org by "David Wood (JIRA)" <ji...@apache.org> on 2008/12/17 17:45:44 UTC
[jira] Created: (IMPERIUS-20) No type match between String and
CharSequence
No type match between String and CharSequence
----------------------------------------------
Key: IMPERIUS-20
URL: https://issues.apache.org/jira/browse/IMPERIUS-20
Project: Imperius
Issue Type: Bug
Environment: WIndows
Reporter: David Wood
Assignee: Bill Stoddard
Attachments: TypeResolver.java.patch
The policy below does not parse and gives an error message on append() because it thinks String does not match CharSequence, which is what StringBuilder.append() is declared to accept. This points out a general problem of matching types against super classes. I have a patch for TypeResolve for String, but this may need to be handled more generically.
Import Class java.lang.StringBuilder:stringBuilder;
Strategy Execute_All_Applicable;
Policy
{
Condition
{
4 == 4
}
Decision
{
stringBuilder.append("O1")
}
}:2;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IMPERIUS-20) No type match between String and
CharSequence
Posted by "Neeraj Joshi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IMPERIUS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658632#action_12658632 ]
Neeraj Joshi commented on IMPERIUS-20:
--------------------------------------
Committed patch. Thanks David sorry for the delay
> No type match between String and CharSequence
> ----------------------------------------------
>
> Key: IMPERIUS-20
> URL: https://issues.apache.org/jira/browse/IMPERIUS-20
> Project: Imperius
> Issue Type: Bug
> Environment: WIndows
> Reporter: David Wood
> Assignee: Bill Stoddard
> Attachments: TypeResolver.java.patch
>
>
> The policy below does not parse and gives an error message on append() because it thinks String does not match CharSequence, which is what StringBuilder.append() is declared to accept. This points out a general problem of matching types against super classes. I have a patch for TypeResolve for String, but this may need to be handled more generically.
> Import Class java.lang.StringBuilder:stringBuilder;
> Strategy Execute_All_Applicable;
> Policy
> {
> Condition
> {
> 4 == 4
> }
> Decision
> {
> stringBuilder.append("O1")
> }
> }:2;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IMPERIUS-20) No type match between String and
CharSequence
Posted by "David Wood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IMPERIUS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Wood updated IMPERIUS-20:
-------------------------------
Attachment: TypeResolver.java.patch
The attached changes TypeResolver to check to see if the thing the String is being assigned to can accept strings. There had been a check for java.lang.Object, but I believe this fix will include that. I've run the build and test cases with success on this change.
> No type match between String and CharSequence
> ----------------------------------------------
>
> Key: IMPERIUS-20
> URL: https://issues.apache.org/jira/browse/IMPERIUS-20
> Project: Imperius
> Issue Type: Bug
> Environment: WIndows
> Reporter: David Wood
> Assignee: Bill Stoddard
> Attachments: TypeResolver.java.patch
>
>
> The policy below does not parse and gives an error message on append() because it thinks String does not match CharSequence, which is what StringBuilder.append() is declared to accept. This points out a general problem of matching types against super classes. I have a patch for TypeResolve for String, but this may need to be handled more generically.
> Import Class java.lang.StringBuilder:stringBuilder;
> Strategy Execute_All_Applicable;
> Policy
> {
> Condition
> {
> 4 == 4
> }
> Decision
> {
> stringBuilder.append("O1")
> }
> }:2;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.