loading...
Bug Busters
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2006.40March/April 2006 (vol. 23 no. 2) pp. 92-93
 This Article 
 
Buy PURCHASE ARTICLE: $19
PDF
HTML
Buy IEEE Xplore Subscribers
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
ASCII Text
x 
 
Diomidis Spinellis, "Bug Busters," IEEE Software, vol. 23, no. 2, pp. 92-93, March/April, 2006.
 
 
BibTex
x
 
@article{ 10.1109/MS.2006.40,
author = {Diomidis Spinellis},
title = {Bug Busters},
journal ={IEEE Software},
volume = {23},
number = {2},
issn = {0740-7459},
year = {2006},
pages = {92-93},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2006.40},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Bug Busters
IS - 2
SN - 0740-7459
SP92
EP93
EPD - 92-93
A1 - Diomidis Spinellis,
PY - 2006
KW - errors
KW - bugs
KW - tools
KW - Lint
KW - type checking
KW - annotations
VL - 23
JA - IEEE Software
ER -
 
One way to deal with bugs is to avoid them entirely through stringent quality control. To conserve our valuable resources, we can use tools to catch the bugs before they end-up in production code. We can use type-safe languages, pay attention to compiler warnings, adopt specialized bug-finding tools, or we can adjust our code to make it locate bugs during testing.
Index Terms:
errors, bugs, tools, Lint, type checking, annotations
Citation:
Diomidis Spinellis, "Bug Busters," IEEE Software, vol. 23, no. 2, pp. 92-93, Mar./Apr. 2006, doi:10.1109/MS.2006.40
Usage of this product signifies your acceptance of the Terms of Use.