Re: type Foo_ptr in new void*;

["Warren W. Gay VE3WWG" <ve3wwg@home.com>]

David Thompson wrote:
> Darren New <dnew@san.rr.com> wrote :
> ...
> Actually writing different definitions in two different sources
> is fairly obvious, but there are subtler ways to screw up.
> One is to change the definition in a .h file and recompile
> some but not all of the .c's that use it; tools like make
> help with this.  Another is to have two same-named .h files
> in different directories/subtrees and select a wrong one.
> A third is to actually include the correct and same .h
> but it in turn uses #define's which are set differently
> (a coworker recently lost several days to that last;
> even a full de novo build doesn't catch or fix it).

Another way to have this happen, is to have a "private"
definition as the "proper type" which is used internally
by the library, and an incorrect "opaque type" defined 
for public use. Or, this may have been correctly (but not
portably) defined, but did not port correctly to the 
new platform.

-- 
Warren W. Gay VE3WWG
http://members.home.net/ve3wwg