1. "static globals stay in the same file they are defined in."
2. "static locals stay allocated even when the function they're defined in is not being executed."
While maintaining backward compatibility is good, this does make the language confusing. Static is probably one of the worst offenders, but I think that C++ especially has quite a few of these cases now.
- thread
- type
- class
- module
- functor
- virtual machine
- ...So if someone is 'confused' by the fact that a keyword has two different (albeit related meanings) in the language, and is too bothered to check a manual, or the internet for an explanation, how is that person supposed to write a driver or an operating system, or use low level ipc/communication mechanisms, or debug an elusive deadlock? C is not JavaScript, get over it.