Named pipes? That sounds like a case of overkill. When AXIS generates the preview, the g-code interpreter lives in the same address space, so any kind of in-memory structure is going to be fine. For instance, a linked list or array of frames, each containing a filename, line number, and the "local" variables. Plus a way to access the "global" variables.
Right now the interpreter has strings that are marked for translation, but it does no translation itself. Instead, when the GUI gets the error message by number, it looks it up in the catalog. But if the message has been formatted (e.g., turned from "X coordinate %f is too big" to "X coordinate 1000 is too big") then it can't simply be looked up in the catalog. This means adding to the interpreter the step that looks up the format string to find the translated format string. I suggest getting rid of the 100 or so different numbered errors because it is a needless complication to have two ways to look up an error: One by looking up an entry in a table based on the number, and another by looking in some buffer for a string. Throw out the old cruft when you replace it. Don't keep the old cruft around forever. (at least as far as the mostly-internal API is concerned, I'm not suggesting that you break compatability with old g-codes) Jeff ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
