The Problem (in general)
Regardless, it can lead to problems.
Issues start to arise during the actual conversion process. As I mentioned, semicolons are not actually inserted into the token stream. This means that if the token conversion process is looking for a terminating semicolon, errors can be generated when one is not found.
In most cases we have constructed the token conversion process to take this situation into account, but there are probably edge cases where the code is written in such a way as to cause a conversion failure.
If you run into this situation, then please send us the code segment that is causing the issue and we’ll work to create a fix.
In general, when performing the conversion from CRM 4.0 to CRM 2011, it’s a perfect time to fix any code-design issues you might find. So, keep an eye out for the missing semicolons and add them where required.
7.9.1 Rules of Automatic Semicolon Insertion