On Mon, 12 Apr 2021 at 11:41, M.-A. Lemburg <mal@egenix.com> wrote:
Right, except that in practice:
1) Many useful libraries are not documented or properly documented.
In those cases, I'd argue that such libraries then do not really care for a specific public API either :-)
2) People don't read the docs (at least not always, and/or not in details).
Uhm, how can you write code against a package without knowing how it is used ?
Is the problem here that we're trying to apply a technical solution to what is, in practice, a people problem? I don't think I've ever seen (in any language) a system of declaring names as public/private/whatever that substituted well for writing (and reading!) good documentation... At best, hiding stuff makes people work a bit harder to write bad code :-) Paul