Community
Participate
Working Groups
Several files in the JS runtime are generated from the IRs in the system parts. For example, exceptions. They're currently being generated with the regular JS generator, so no debug information is available (the exceptions have no fields). Low cost solution: From now on, generate with the dev-mode generator and make sure any functions that it reference are defined in egl.js (we already have a stub for egl.atline(), would also need at least egl.addLocalFunctionVariable and egl.setLocalFunctionVariable). Deployed code would have this extra debug information in the code. The solution below would then be implemented for 1.0. Better solution: Update either the eglar script or the build process to automatically generate certain IRs into the jsrt project. It would invoke both the regular js generator into the runtime directory, and the js-dev generator into a runtime-dev directory. The DebugFileLocator gets updated to first check for a file in runtime-dev, then falls back on runtime.
Lisa - I don't think this is an enhancement - it's a problem with the way we are manually generating the system parts for the JavaScript runtime. RUI debug's display of these parts is broken until we address this.
Rolling forward to I-15
Debug information has been added to the generated runtime files. They each now have eze$$getChildVariables and eze$$getName.
Verified
