Skip to content

Commit 2f47e11

Browse files
Update 2017-4-8-debugging-in-c.md
1 parent f57f32c commit 2f47e11

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

_posts/2017-4-8-debugging-in-c.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@ comments: true
1111
---
1212
# Dare To Debug
1313

14+
Taken from: Let Us C, page 638 -644
15+
1416
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!
1517

1618

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

9698
</blockquote>
97-
98-
# Note
99-
100-
If you found similar contents in the book Let Us C, page 638 -644, It is a pure accident.
101-
102-
Looking for C examples [Visit Novice Programmers](https://www.aakrist.me)

0 commit comments

Comments
 (0)