In the above example, I think it's more reasonable to get the official correct spelling, and have everyone learn a bit of spelling, than to use aliasing.
In the general case, you're assuming that a) there are tests to run, and, more importantly, b) that the tests have 100% coverage. While there may not be a lot of pity for the fool (apologies to Mr. T) in the first situation, the latter is much more realistic. Getting to 100% coverage is difficult, if not actually impossible once you've released a module and others may be using it beyond your ability to test/modify. Sometimes the alias is fixing what breaks. Then again, in this situation, search-and-replace doesn't really work, either.
In reply to Re^3: Trying to understand aliasing (*var)
by Tanktalus
in thread Trying to understand aliasing (*var)
by tphyahoo
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |