I think it works even better if you can get help from the type system. For example, the SafeHtml interface in GWT [1] gives you some safety from Java's type checking and can also make additional static analysis easier. (Then it becomes an exercise in making sure the API is used as intended.)
Perhaps something similar could be done using typedefs in C?
Comments
I think it works even better if you can get help from the type system. For example, the SafeHtml interface in GWT [1] gives you some safety from Java's type checking and can also make additional static analysis easier. (Then it becomes an exercise in making sure the API is used as intended.)
Perhaps something similar could be done using typedefs in C?
[1] http://www.gwtproject.org/javadoc/latest/com/google/gwt/safe...
Typedefs in C are just aliases, so given `typedef int foo;` one can freely use `int`s and `foo`s interchangeably, i.e. no checking by the compiler.
That said, one could use actual wrapper structs around the various types.
A static analysis framework could treat certain typedefs specially since it's parsing the C code anyway.
Great idea! Too bad openssl uses #define instead
There's also sparse[0]'s address space annotation, which Linux uses for annotating data from userspace.
[0] https://git.kernel.org/cgit/devel/sparse/sparse.git/