Quote:
Originally Posted by smithdale87
They do throw warnings, but that's just because the compiler doesn't know the method exists. All you have to do is define the methods in a header file, and the warnings will go away.
|
how does apple know you used this function instead of anotheir ?
I don't know the apple/iphone linkage or dynamic library so my opinion is based on experience of other system : if I have to test an application which I only have the binary, and this application is using dynamic library; I add a special mode or a proxy for those library to know which library is used and in librabry which function is used
I would not be surprised that apple have, for every function in library, a call to a generic trace function while entering and quitting every function (*). Then the amount of work to check if you are using some undocumented function is 'nil'
I don't know if I made it clear to understand
greg
(*) sound to be a lot of work, but when you debug a huge project, using many people work, it's a great help to read this trace (indented...) to find which function has been called before.
