Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 356123 - Equivalence of egl.lang.EglString and eglx.lang.EString
Summary: Equivalence of egl.lang.EglString and eglx.lang.EString
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 354617
  Show dependency tree
 
Reported: 2011-08-29 17:48 EDT by Scott Greer CLA
Modified: 2017-02-23 14:15 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Greer CLA 2011-08-29 17:48:56 EDT 
In the FVT testcases there is this:

			a AnyException = new AnyException;  
			a.messageID = "THROWIT";

JavaScript is generating this as an ezeCast, which is completely bogus.  The root problem is that somewhere in the compiler / MOF model, it doesn't understand the inherent equivalency of these two types so it produces an implicit AsExpression.

I've spoken to Paul about this and he agrees that this is a bug.
Comment 1 Paul Harmon CLA 2011-08-30 11:31:25 EDT 
I have updated IRUtils to check for the types EBoolean/EGLBoolean and EString/EGLString. These types are now considered to be equivalent, so no AS expression will be created.
Comment 2 Scott Greer CLA 2011-08-30 17:36:58 EDT 
Verified