> Personally i dont quite understand why APIs arent protected inthe same > manner as the implementation. What exactly is the difference between > typing a method signature and typing some code inside the method > body ? In reality both define the product, change either and you have > a very something different. It may be broken, or have changed > behaviour but its ultimately quite different. Its quite evident that > studying one by some method of reverse engineering one can learn about > the system and how it works etc, which includes the discovering APIs. > Regardless of whether an API is public or private its still part of > the package.
An API which you can't compile up against, isn't very useful though! A programmer could manually introspect the C files and make the headers himself, but in Google's case, that would be over 700 files. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
