Re: Code fails with Segmentation Fault
- From: "David T. Ashley" <dta@xxxxxxxx>
- Date: Tue, 28 Nov 2006 13:35:40 -0500
"santosh" <santosh.k83@xxxxxxxxx> wrote in message
news:1164737014.901040.130440@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
But for very small programs, such as those you write when you start
learning C, it might be better to mentally "run" the program, rather
than fire up a debugger at a hint of the least problem.
Most of the senior citizens in computer science endorse that point of view.
Careful code inspections will get you more bang for your buck than anything
else.
Some of the senior citizens remember the days when the FORTRAN compiler was
only run twice per day on the shared mini-computer, so the students would
pay careful attention to getting programs (i.e. stacks of punch cards) right
the first time.
It may have been Knuth who said something like "The last thing the world
needs is more highly-interactive programming environments".
As the edit-compile-run cycle gets faster, people get more and more
careless.
.
- Follow-Ups:
- Re: Code fails with Segmentation Fault
- From: Tom St Denis
- Re: Code fails with Segmentation Fault
- References:
- Code fails with Segmentation Fault
- From: Vlad Dogaru
- Re: Code fails with Segmentation Fault
- From: Bill Medland
- Re: Code fails with Segmentation Fault
- From: Tom St Denis
- Re: Code fails with Segmentation Fault
- From: santosh
- Code fails with Segmentation Fault
- Prev by Date: Re: Macros
- Next by Date: Bytes allocated by the code ??
- Previous by thread: Re: Code fails with Segmentation Fault
- Next by thread: Re: Code fails with Segmentation Fault
- Index(es):