The sos home page

Bugs and problems

If the compiler complains about duplicate case labels, group the duplicate labels together and write some old "if..else if..else" C code to separate between them. A better option is to have a nested switch statement controlled by a different segment of the case labels, e.g. *(sp+10). Such problems should be relatively rare.
With a compiler that doesn't support "long long" in switches we get down to five significant characters and that is less than satisfactory. Do C99 require support of long long in switches?
The limit of 10 significant characters is far from ideal yet it may prove to be not too bad in practice.

There may still be problems with char signedness...
Hiding the integer encodings of strings with "#define" directives of the same strings is convenient. However, there is a danger of redefining C keywords or function and variable names.
Quiz: is it possible that some standard conforming compiler wouldn't complain on replacing a C keyword or a name token with an integer constant?
A good safety measure is to use uppercase case labels and convert lowercase input strings before processing.
The sos generated CPP code includes a check against redefining macros (e.g. NULL). To be effective the sos code should be included/inserted after all headers and other C preprocessor code. The check code (not shown in the example) will halt compilation with an error message.
To completely eliminate the "redefinition danger" use the "-s" option and generate a switch code skeleton.
We must feed the sos program with the list of strings in order to calculate the integers. It's inconvenient. A special pre-processor may solve this.