I'm not sure that this is in great demand. Assuming you have a compiler worth its salt, then you'll know if you spell a variable name incorrectly or swapped a couple of letters in a function call. But imagine if you did indeed have a code spell checker, how would you implement it?
While browsing through some header files (like I do), I found an example of a solution to the spell checking problem. Here it is:
/
__exceptthat
Given a set of annotations Q containing __exceptthat maybeP, the effect of
the except clause is to erase any P or notP annotations (explicit or
implied) within Q at the same level of dereferencing that the except
clause appears, and to replace it with maybeP.
Example 1: __valid __exceptthat __maybenull on a pointer p means that the
pointer may be null, and is otherwise valid, thus overriding
the implicit notnull annotation implied by __valid on
pointers.
Example 2: __valid __deref __exceptthat __maybenull on an int **p means
that p is not null (implied by valid), but the elements
pointed to by p could be null, and are otherwise valid.
/
#define __exceptthat __declspec("SAL_except")
#define __execeptthat __exceptthat
I'm just wondering what's going through your head when you're writing in that bit of code. "Well, I could go through and fix all of the spelling errors. I know where they are, and any fix is going to require me to recompile this and the dependent code. Let's just make the incorrect spelling work."
Neat huh?
