>At the risk of starting another flame war, I would strongly discourage use of >INTERPRET.
While I used to have that bias, I have since found valid uses for it. >While it may work correctly in some instances, it leads to problems in >general, and is easily replaced by "value()". This sounds Knee-Jerk. >I first ran across this problem while working at an ISV, and had to maintain >code designed to manipulate JCL. >The author used an INTERPRET that >self-destructed the first time it encountered a JCL comment. Is this a problem with INTERPRET, or a problem with programming/testing skills? - I'm a SuperHero with neither powers, nor motivation! Kimota! ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
