On 6/8/2012 12:14 PM, Dave Caroline wrote:
I hadn't looked at this routine until you brought it up but there's some seriously crappy code in CLPRNT.FOR. You're looking at its hind end. I've got to go out for a while but I'll get back to it tonight.On Fri, Jun 8, 2012 at 5:05 PM, Jon Elson<elson@xxxxxxxxxxxxxxxx> wrote:Dave Caroline wrote:given this fragment from CLPRINT.FOR WRITE(6,1) 1 FORMAT(' ERROR IN SECOND ARELEM') what is WRITE(6,1) doing? is it printing the variable passed in?It prints ' ERROR IN SECOND ARELEM' verbatim, there is no variable supplied after the ")" and no variable format info on format line (1). JonI agree so that means buggy calling lines, or the writer intended changing it later. as the manual implies it prints sensible messages and the code otherwise. Dave Caroline
I think I've said it before, but the APT360 source code looks to me like it has been through the hands of many programmers over time and without the benefit of adult supervision. What a pain. Not that it would change anything now but I wish I knew how much is due to the IITRI/CAM-I and how much IBM. I have to keep reminding myself that it "works."
Regards, Kent
