Al, I agree that it would be good to do it as you program. But I have inherited a system and I'm not the original programmer. So the output of problems to a file is a great help.
What I would like it to do is flag any variables that are reserved words. This programmer used very short variables and I am afraid that some might be a reserved word. I don't like the prospect of eyeballing every program. Is it possible to read in the list of reserved words, then write a program to parse every variable? Bernie Lis Megabytes, Inc. ----- Original Message ----- From: "Albert Berry" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, August 12, 2002 6:30 PM Subject: Re: I Like It! I Like It > Bernie, I tend to code and run RSTYLE at the same time. I have the file open in a text editor, type away, save the file, click on my DOS window, RSTYLE the code file, trace the file, back to the editor and repeat. I have a lovely habit of counting parentheses incorrectly, so this saves me a bunch of time. > ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
