Do you consider that the cost of adding the tests to prevent this -- at every place where a package name can appear, at compile time or runtime -- would be worth having, in order to prevent this perfectly logical -- if weird -- possibility?
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP Neil Armstrong