CF2016 Updater 3

Over the course of several months we identified some date/time issues that also exist in CF10 and CF11. In CF10 and CF11 there are still more inconsistency issues like in CF2016. Some of the date/time formatter and parser issues have been fixed in CF2016 RTM, but it was still a mess and the functions are not behaving as expected in many cases. We are still in discussion about incorrect IsNumericDate() results not listed below. Please also see ColdFusion 2016: Upcoming new IsDateObject() function that was a result of the issues we faced with below bugs.

Notable changes are:

The functions IsDate() / LSIsDate() / ParseDateTime() / LSIsDate() require that you provide a string to these functions. However these functions do not throw an exception if you provide a date/time object. Not only this - they return inconsistent results if you use an object - often it works, but not always. So you may feel like the function allows an object as param and you learn later the hard way that your code is not always behaving properly. The bad about this issue is that there exists no function that allows you to check if you have a valid ColdFusion date/time object or just a date/time string.