"Any language which allows a typo in an assignment statement to create a new variable name binding silently is insufficiently safe for my purposes." Um...Perl

"Any language which allows a typo in an assignment statement to create a new variable name binding silently is insufficiently safe for my purposes." Um...Perl has exactly this problem. The only difference is that it's worse because the variable in question gets created as a global variable of the local package - which is naturally visible to anything else that wants to see it, btw. This is exactly why they created "use strict", and underscores the "Perl philosophy" in an elegant nutshell - instead of fixing the underlying problem, just create a hack around it and expect everyone to "know" that they should use it as a best practice.