Software Engineering
Keith Thompson's user avatar
Keith Thompson's user avatar
Keith Thompson's user avatar
Keith Thompson
  • Member for 11 years, 8 months
  • Last seen more than a month ago
Profile Activity
Stats
6,402
reputation
335k
reached
44
answers
0
questions
Communities
View all
About

I'm a programmer and all-around nerd living in San Diego, California.
I'm currently working at Philips.

E-mail: Keith.S.Thompson@gmail.com

Badges
View all badges
2
gold badges
28
silver badges
35
bronze badges
Top tags
View all tags
175
Score
5
Posts
11
Posts %
170
Score
11
Posts
25
Posts %
135
Score
8
Posts
18
Posts %
101
Score
7
Posts
16
Posts %
63
Score
2
Posts
5
Posts %
52
Score
4
Posts
9
Posts %
Top posts
View all questions and answers
All Questions Answers
Score Newest
answer
120
Should developers enter bugs into the bug tracking system?
Feb 23, 2012
answer
82
Why Use !boolean_variable Over boolean_variable == false
Feb 25, 2012
answer
67
typedefs and #defines
Jan 18, 2012
answer
59
Is using goto ever worthwhile?
Feb 6, 2012
answer
44
Is it necessary to read every single byte to check if a copied file is identical to the original?
Dec 3, 2011
answer
30
Array or Malloc?
Apr 11, 2012
answer
30
Non-zero exit status for clean exit
Jun 22, 2012
answer
28
Why can't `main` return a double or String rather than int or void?
Jun 29, 2013
answer
20
What is the difference between a pointer pointing to 0x0 location and a pointer set to NULL?
Jan 5, 2012
answer
20
What's the effect of this assignment (whatever the language)?
Feb 14, 2013
Top network posts
View all network posts
1088
Is there a foreach loop in Go?
1018
Why does the C preprocessor interpret the word "linux" as the constant "1"?
673
"echo -n" prints "-n"
618
How to conditionally do something if a command succeeded or failed
606
Why is it better to use "#!/usr/bin/env NAME" instead of "#!/path/to/NAME" as my shebang?

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.