Community
Participate
Working Groups
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.
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.
+1 I agree.
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.
Deferring to Future. This won't be done in 0.8.2.