|
> Problem is, sometimes when error fixing, the error fix doesn't work and > introduces a new error, so code may need to be back out. If you dont > comment out your changes, they're lost! well, sometimes i will make a bk version of the program. or create a temorary library for the prior code, if i'm making a bunch of changes. or when you get the program working, then go in and remove the commented code! if you work by yourself, and it doesn't bother you, then whatever. but we have multiple programmers, and when we have to make a quick evaluation of a problem, weeding thru commented code can be a problem. or if you sell your programs as a package! we have a client that purchased a package that has commented code all over the place. but they also still use addrout files for their search files. for you that aren't old timers, that's what we did on the system 34, before you had logical files! nothing like state of the art! nj +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.