Skip to content

Update 2017-4-8-debugging-in-c.md #55

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 5, 2024
Merged

Update 2017-4-8-debugging-in-c.md #55

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 2 additions & 6 deletions _posts/2017-4-8-debugging-in-c.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ comments: true
---
# Dare To Debug

Taken from: Let Us C, page 638 -644

C programmers are great inventors of our times. However, there are is no shortage of horror stories about programs that took twenty times to **DEBUG** as they did to **WRITE**. Many a time programs had to be rewritten all over again because the bugs present in them could not be located. Bugs are C programmer's birththright. But how do we chase them away. No sure-shot way for that. I thought if I make a list of more common programming mistakes, it might be a help. They are not arranged in any particular order. But as you realize, surely a great help!


Expand Down Expand Up @@ -94,9 +96,3 @@ Programming is not about being clever and obscure -- it's about how clearly your
<blockquote> Any person can write the program which computer can understad, but real programmer write program which human can understand.

</blockquote>

# Note

If you found similar contents in the book Let Us C, page 638 -644, It is a pure accident.

Looking for C examples [Visit Novice Programmers](https://www.aakrist.me)