Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344020 - Generated methods can clash with runtime methods
Summary: Generated methods can clash with runtime methods
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-27 14:49 EDT by Justin Spadea CLA
Modified: 2017-02-23 14:14 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Spadea CLA 2011-04-27 14:49:18 EDT
Either aliasing needs to be done on certain generated method names, or all the runtime methods need to start with something that's not allowed in EGL (e.g. "eze" prefix).

The following function in a basic program will cause a compile error, because it's the same name as a super method (and the super method has a return type, this does not):

function _inputRecord()
end

Whatever happens, make sure the function name is consistent in the SMAP.
Comment 1 Jeff Douglas CLA 2011-07-12 11:13:33 EDT
It seems to me that the best approach is to change the runtime methods to always start with eze or something, instead of altering the user's method names. They might require their name to be kept intact.
Comment 2 Matt Heitz CLA 2011-07-12 11:22:18 EDT
+1  I agree.
Comment 3 Brian Svihovec CLA 2011-12-16 15:50:57 EST
Will and I discussed this issue, and we agreed that it would be ok to alias code generated from our system libraries, but that we should not alias code generated from a users EGL source.  This could possibly be done with a compiler argument to indicate that all generated code should be aliased or not.
Comment 4 Matt Heitz CLA 2013-01-03 14:01:48 EST
Deferring to Future.  This won't be done in 0.8.2.