Michael, the control flow is this: > > what happens here: Python calls back into the interpreter C++ code to > parse and execute this line. Since <string> is basically a new block, it > must save the current block context, do the job, restore the current block > context, return. That's where the design restrictions kick in: recursion > wasnt on the feature list.
Ok, your explanation makes it much more clear what's happening. remapping was designed to fix exactly this very issue: folks come up with > some ideas, patch the interpreter in C++, support issues happen. With > remapping, and staying in the Python context, you can do all this without > changing the interpreter binary proper - it is just impossible to integrate > every special-purpose solution at the C++ level. > > That makes good sense, and fits with my initial intuition. I'll follow your suggestion to get the oword solution working. To test my understanding: is it legitimate for the python mapping code to call canon methods directly? Would that mess up state for the interpreter when it continued executing? Rod ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
