Joe Ess wrote:When I was a lowly programming intern, I heard it said that the MS C compiler the company used was garbage because they always had to use debug settings for their code. If one tried to use the complier options to make code more "compact", the code would crash. Putting the debug settings back would make the issue impossible to reproduce, therefore, it was the compiler's fault. Since this was before the dawn of the Internet, if knowledge wasn't in one of your employee's experience or in the reference manuals on your desk, it was unobtainable. It wasn't until I finished my internship and Java came out that I realized they likely had buffer overruns in their code and the debug code inserted by the compiler was insulating them from the catastrophic consequences.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton