On Sun, Feb 25, 2007 at 11:06:02AM -0600, Ray Henry wrote: > > In the case shown in the image linked above, the interpreter > would have to hold two commands and ask how the second affected the > first.
It's actually worse than this. Imagine a program that moves the cutter into a concave corner, and then moves up and down a hundred times, then continues to the next corner. To figure out where to stop on the first move, you have to look ahead past the hundred up and down moves. At first I thought "well, just don't allow that kind of motion in a concave corner" but you don't even know if it's concave until you do the lookahead. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
