Building custom static checkers using declarative programming

Ian D Horswill; Robert Zubek; Matthew Viglione

doi:10.4324/9781315151700

Building custom static checkers using declarative programming

Ian D Horswill, Robert Zubek, Matthew Viglione

Computer Science

Research output: Chapter in Book/Report/Conference proceeding › Chapter

Abstract

Programmers have developed a wide range of tools for sanity checking their code. Compilers perform type checking and generate warnings about undefined or unused variables. Programs such as Microsoft’s FxCop can detect opportunities for optimization, likely bugs such as files that are opened but never closed, and the use of unlocalized strings. These are all examples of static checking, as opposed to dynamic checks (such as assertions) that can only verify behavior for a particular run of the program.

Original language	English (US)
Title of host publication	Game AI Pro 3
Subtitle of host publication	Collected Wisdom of Game AI Professionals
Publisher	CRC Press
Pages	487-496
Number of pages	10
ISBN (Electronic)	9781498742597
ISBN (Print)	9781498742580
DOIs	https://doi.org/10.4324/9781315151700
State	Published - Jan 1 2017

ASJC Scopus subject areas

Computer Science(all)

Access to Document

10.4324/9781315151700

Cite this

Horswill, I. D., Zubek, R., & Viglione, M. (2017). Building custom static checkers using declarative programming. In Game AI Pro 3: Collected Wisdom of Game AI Professionals (pp. 487-496). CRC Press. https://doi.org/10.4324/9781315151700

@inbook{080a4b0dfa634d7e849d2d7622f1f405,

title = "Building custom static checkers using declarative programming",

abstract = "Programmers have developed a wide range of tools for sanity checking their code. Compilers perform type checking and generate warnings about undefined or unused variables. Programs such as Microsoft{\textquoteright}s FxCop can detect opportunities for optimization, likely bugs such as files that are opened but never closed, and the use of unlocalized strings. These are all examples of static checking, as opposed to dynamic checks (such as assertions) that can only verify behavior for a particular run of the program.",

author = "Horswill, {Ian D} and Robert Zubek and Matthew Viglione",

year = "2017",

month = jan,

day = "1",

doi = "10.4324/9781315151700",

language = "English (US)",

isbn = "9781498742580",

pages = "487--496",

booktitle = "Game AI Pro 3",

publisher = "CRC Press",

}

TY - CHAP

T1 - Building custom static checkers using declarative programming

AU - Horswill, Ian D

AU - Zubek, Robert

AU - Viglione, Matthew

PY - 2017/1/1

Y1 - 2017/1/1

N2 - Programmers have developed a wide range of tools for sanity checking their code. Compilers perform type checking and generate warnings about undefined or unused variables. Programs such as Microsoft’s FxCop can detect opportunities for optimization, likely bugs such as files that are opened but never closed, and the use of unlocalized strings. These are all examples of static checking, as opposed to dynamic checks (such as assertions) that can only verify behavior for a particular run of the program.

AB - Programmers have developed a wide range of tools for sanity checking their code. Compilers perform type checking and generate warnings about undefined or unused variables. Programs such as Microsoft’s FxCop can detect opportunities for optimization, likely bugs such as files that are opened but never closed, and the use of unlocalized strings. These are all examples of static checking, as opposed to dynamic checks (such as assertions) that can only verify behavior for a particular run of the program.

UR - http://www.scopus.com/inward/record.url?scp=85052603781&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=85052603781&partnerID=8YFLogxK

U2 - 10.4324/9781315151700

DO - 10.4324/9781315151700

M3 - Chapter

AN - SCOPUS:85052603781

SN - 9781498742580

SP - 487

EP - 496

BT - Game AI Pro 3

PB - CRC Press

ER -