On Friday 22 July 2016 13:52:59 Kenneth Lerman wrote: > Andy is exactly right -- and this is the way it should work. > > The real question is what might one do to let users have the > functionality that Gene wants. If I were to do that, I would > incorporate it into re-architecting the interpreter. It's important to > remember that this code was originally designed and written in the > distant past when memory was limited and expensive. > > If we wanted to, we could take every variable and copy its present > value into the runtime queue. Then we could provide a way of accessing > the variables in the queue. > > We could do a lot. But it would need to be part of a major rewrite. > That requires someone with the skills, the time, and the interest. > > Ken
You know way more than I do about the innards, Kenneth, so I'll rebutt this by saying that it worked as expected before the axis/joints merge, and now it doesn't. Printed inline as the code is running looks like the right answers. Hit the esc to stop it, and Andy is right, it prints that value AFTER the WHILE loop has executed. To me there is a connection to the merge my mind can't ignore. But as I've said quite a few times before, my oar at steering this is not as big as a toothpick. But if the debug containing that value has scrolled off the top of the limited space, doing a restart from where one hit the esc key is quite difficult, and reduces the usefullness of doing a onsie with LCNC less than fun. > On Wed, Jul 20, 2016 at 8:21 AM, Gene Heskett <[email protected]> wrote: > > On Wednesday 20 July 2016 05:21:03 Sarah Armstrong wrote: > > > Gene > > > is this where your working in radius mode , but the dro is showing > > > dia mode ? > > > or am i off the mark > > > > I was working in radius mode, yes, but the on-screen DRO reports > > both rad and dia. So I believe that Andy has hit it since the loop > > increment at the time was .01mm in rad mode. So if the lookahead was > > causing it to report the value after the WHILE exited, that makes > > the best sense I could get out of it too. But that reported value > > would have taken the program a few dozen passes thru a loop that > > took about 5 minutes to execute per pass before it would have been > > actually reached. So obviously LCNC is working from 2 different > > copies of the var, and the MDI query returned the wrong copy. But > > thats just a SWAG of course. > > > > Perhaps Andy can tell us? > > > > > On 20 July 2016 at 09:39, andy pugh <[email protected]> wrote: > > > > On 20 July 2016 at 03:59, Gene Heskett <[email protected]> wrote: > > > > > By then the DRO said the radius was in the 1.26 area. But, on > > > > > the mdi screen, I still got that 2.41. There's a 2.40 as the > > > > > while compare, but there is not a 2.41 anyplace in the code. > > > > > > > > It sounds like the MDI window is reporting the value in the > > > > variable after the interpreter lookahead has exited the loop. > > > > > > > > -- > > > > atp > > > > Thanks. > > > > Cheers, Gene Heskett > > -- > > "There are four boxes to be used in defense of liberty: > > soap, ballot, jury, and ammo. Please use in that order." > > -Ed Howdershelt (Author) > > Genes Web page <http://geneslinuxbox.net:6309/gene> > > > > > > -------------------------------------------------------------------- > >---------- What NetFlow Analyzer can do for you? Monitors network > > bandwidth and traffic > > patterns at an interface-level. Reveals which users, apps, and > > protocols are > > consuming the most bandwidth. Provides multi-vendor support for > > NetFlow, J-Flow, sFlow and other flows. Make informed decisions > > using capacity planning > > reports.http://sdm.link/zohodev2dev > > _______________________________________________ > > Emc-developers mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/emc-developers Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
