But yes, jni is in violation of these rules by defining global names starting with an underscore.
So is the xorg code. So is the Linux kernel code, I believe. And I have no doubt that you'll quickly find dozens of other projects that have the same problem.
That poor rule must be the most-ignored one in the C standard.
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
To be fair, the actual rule allows names beginning with a single underscore followed by a lower-case letter. In C, at least -- I don't know about C++.Originally Posted by CornedBee
Having said that, I find the rule almost tyrannical. They could have simply reserved all names beginning with a double underscore, and allowed everybody else to use the underscore just like they do -- to indicate that a name is part of internal implementation details.
It seems like the motivation was entirely backwards. It gives the standard library creators an easy way to "protect" internal symbols and at the same time screws the actual users of the language into inventing goofy ways of doing the same thing. I hate it, honestly.
