Can I force a compiler error if certain functions are called?

Question

I have v1 and v2 versions of my software. v1 uses the registry to save settings, with lots of calls to GetProfileInt, etc. v2 now uses an sqlite db to save settings.

<

Answer 1

I believe you could #define GetProfileInt(a, b, c) "don't use this"; after #include'ing Windows.h.

Since GetProfileInt is a macro for routing to the proper function, this would result in a macro redefinition. And since char[] can't be assigned to UINT, the compiler error's.

It's a dirty, dirty hack though, I feel like taking a shower for discussing it.