I remember my first official University programming course. We were to learn the language Pascal. Pascal is a socalled "teaching" programming language primarily to teach structured programming.
During the first semester we learned a lot about syntax and conditions, looping, and a whole bunch of other things. An incredibly important, in the eyes of our professor, was the subject of variable notation. He was a die-hard fan of the Hungarian Notation, I remember receiving poor marks on a perfectly running code assignment because my variables were not appropriately named. This method of variable naming or prefixing resolved itself later into my professional life into mainly just CamelCase and followed on into Java naming conventions. Java naming conventions are fine in a case sensitive language but only help to increase readability in a case in-sensitive language like Coldfusion.
I then noticed a blog post by Sami Hoda about how CF9 doesn't like Mango Blog. In his blog post he mentions a couple of errors that led me to believe that the programmers of a couple of the Mango plugins:
- a) Created functions that are now part of CFML and
- b) used variable names that have now become reserved words or functions.
This goes to show that Hungarian Notation still has a very important place in todays programming, if the Developers of Mango blog used Hungarian notation to prefix their variables and functions the likely hood that a conflict would arise due to changes in the core language would be non-existent. If "location" was "strLocation" and ArrayFind() was fnArrayFind() a conflict would have been prevented.
I will be the first one to admit that I don't use the full Hungarian Notation, but i do follow the official declared guidelines at my place of work.
The upgrade problems seen in Mango Blog highlight the need for programmers to be aware that they should also code for the future, not just the now.
No recent entries.