In a recent note, Bill Klein said: > Date: Tue, 30 Aug 2005 14:29:58 -0500 > > <[log in to unmask]> wrote in message > news:<[log in to unmask]>... > > As the missing source code problem is popping up now and then, I'm > thinking that maybe it would be a good idea to include the source code > (compressed) in the load module, like you could do when compiling REXX > programs. This would guarantee that you always have a source code matching > the running programs. > What a concept! Such information would, of course, be invaluable to a source language interactive debugger.
And, long ago, I had the thought that translator output listings ought to be acceptable to the same translator as input. Many programmers use their favorite editor as a listing viewer. Why not, then be able to correct the typo in the same edit session and resubmit that only viewable file to the translator? This would require mostly that information added by the translator be so delimited that the translator would ignore it; not even echo it to the listing on the following iteration. That reminds me of "Point and Shoot" editing. Place the cursor on a translator message in the displayed listing; press a PF key, and an edit session opens with the indicated line in the source file centered and highlighted. HLASM provides sufficient information in the listing to do this (unless the source is in HFS); has anyone implemented it? Other mainframe languages? I did it once for a truly odd couple: Mainsail and XEDIT under VM/CMS. BASIC and LightSpeed Pascal took the complementary approach: they save nothing but the object code; the editable source is generated by decompilation. -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
