| Summary: | The javaName annotation for external JavaObject functions is missing | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Jeff Douglas <jeffdouglas> |
| Component: | EDT | Assignee: | Matt Heitz <mheitz> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | carrollk, greer, jqian, jspadea, mheitz, tww |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
Done, but I called it externalName instead of javaName. I also renamed the javaName field of JavaObject to externalName, and renamed JavaScriptObject's javaScriptName to externalName. Now everything is consistent and we don't need both a javaName and javaScriptName: two annotations which serve the same purpose, and won't work for other languages. I considered calling it "alias" but decided not to since the name in EGL is more of an alias then the value of externalName. I mentioned the new name on the wiki at http://wiki.eclipse.org/EDT:EGL_Language_Stereotypes_and_Annotations (it's footnote #4). I updated the Java generator to use the new name. I didn't find any references to javaScriptName in the JavaScript generator, so it hasn't been touched. NOTE: the Java generator hasn't yet been updated to recognize externalName on fields and functions, but that's outside the scope of this bug. *** Bug 354771 has been marked as a duplicate of this bug. *** closing this defect, which was fixed several months ago |
This javaName alias for the function was allowed in RBD and seems to be missing for EDT. Here's the example code .... the javaName="handler" part is not allowed. package x; externaltype myET type JavaObject{packageName="etPkg", javaName="etName"} function test(); function alias(){javaName="handler"}; end program c2 e myET{}; function main() e.alias(); i int = 14; end end