Watts further notes that introducing status flags testing in the caller, as single-exit structured programming or even ( multi-exit ) return sequencers would entail, results in a situation where " the application code tends to get cluttered by tests of status flags " and that " the programmer might forgetfully or lazily omit to test a status flag.