Greetings all;

Skimming thru the doc pdf, under functions on page 204, I see there is an 
EXISTS[#<named variable>] function that I propose to make use of.

The one big file that carves the ends of all 4 major board parts of the 
blanket chest, uses just 2 variables at the top of the file to control 
which of the 4 boards it is carving during this invocation.

This means a goodly number of trips into the editor in order to set them.

Experimentally I have found that these variables seem to be able to 
survive in memory unless a full powerdown reboot has been done. That 
surprised me when I found that several years ago and it appears to be 
true yet today.

So, what I am considering doing is writing 4 individual 8 or 10 line .ngc 
scripts that set these values into the 2 named variables so that I can 
then remove the creation of these vars from the main file and use only 
what the 10 liners have left behind, thereby removing the need to edit 
any of those 5 files to run it in whatever configuration one of the 4 
new files sets it to.  The exists[] would be used to trigger an 
unconfigured message to the big dummy that I can't run it after a 
powerdown without first running one of the 4 config .ngc files.

Is this practical, or am I playing with fire?

Thanks all;

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>

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to