For example, consider the following:
After writing lines, write some of the write-offs. Do we have to do it like that? Or just it's okay:
After writing 1 lines, write something from something when I can not read or end in Since then, I do not get any compiler warnings collected without end-written compiler warning.
Can anyone help me?
END-WRITE is required only when INVALID KEY < / Code> or not INVALID key is used.
In this you do not need it anymore Although you can always use always if you want
I Do not use INVALID key / not INVALID key , and never use END-WRITE (or END-READ , < Code> END-Open , END-CLOSE , END-START ). Instead I use the FILE status statement on the SELECT , and test the FILE status area after each IO operation.
If you write modern cobalt (1985 standard), you should avoid as many full-stop / duration as you can in the process division After paragraph / section label after the caretaker division heading, before the paragraph / section label, if not used for any other reason at the end of the program.
For the first one of the paragraph / section label, I call it full-stop in column 12 /
No comments:
Post a Comment