|
Reminds me of when I was recompiling a library, just to make sure all the programs were fresh. One program wouldn't compile. But the executable was still there. I looked into the source code listing and found some error 30 bugs. Doing a little bit of research I found the old programmer had decided anything "only" level 30 wasn't enough to worry about, and he had set his default to 40, anything with errors level 40 and above wouldn't compile. Me, mine is error 10, if it has error level 10's, it won't compile (or maybe it's 20, now I don't remember). Looking at the bug, it explained a lot about this programs extremely strange behavior at times. I fixed the bug, and recompiled it, and it then ran fine. But, hey, he had got it to compile... Regards, Jim Langston DAsmussen@aol.com wrote: > <SNIP> > You forgot one: > > - Hey, it compiled didn't it? +--- | 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.