Greetings all;
I'll reiterate my question of yesterday. Section 5.5.7 says for returned data, that a global var named <_value> containing that dara is created, and it is. It also states that another global var named <_value_returned> is created and set to 1. So if its unknown to the potential user of that data, it makes sense to: o001 IF [#<_value_returned> gt .5] to find out if #<_value> contains valid data. However, if the correction has been done, and it should not be allowed to be reaplied if the code is restarted, it makes sense to zero <_value_returned>. But that gets a complaint that its a read-only value and of course the code won't run. So I repeat, what good is it to deny the clearing of that data as a means of preventing its re-use if its reuse could/would screw things up? As this particular code now uses the belt and suspenders approach by re-creating the to be modified var as 0.0000000, before making it = to <_value> the effect of its re-use is not a cumulative error. But it also seems like rather pointless code gymnastics. And that also brings up the situation that exists immediately after a reboot, when there is the possibility of that pair of vars not existing. I'll try that but from the house via ssh, its a hot reboot so the vars should still exist. So thats not a problem, but what about a cold reboot after a power failure. Then the main code won't run, and from the error message generated, no one could be expected to remember that it takes a couple clicks on the align buttons to fix the error. Discussion? 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> _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
