CF-3134331
Title
CF too liberal in what it will cast to a date
Description
Too risky to change anything related to this at this stage. It also has backward compatibility issue and it needs to be thought out and planned well before implementing. Deferring
Comment by Rupesh K.
03/12/2012 08:08:59 GMT
We can evaluate this for the next release
Comment by Vamseekrishna N.
10/03/2016 00:45:57 GMT
I really hope you are referring to the release currently in development to follow CF 2016.
Comment by External U.
10/03/2016 09:41:41 GMT
+1 Found same issue CF 11 update 10 Please fix. <cfif "0001" EQ "000001"> This is not equal </cfif>
Comment by External U.
10/13/2016 09:42:45 GMT
Status:
Closed
Details
Date Created:
03/09/2012
Component:
Language
Version:
Gold Master
Failure Type
Data Corruption
Found In Build:
9.0
Fixed In Build:
2018.0.0.309259
Priority:
Normal
Frequency:
Some users will encounter
System:
Win XP All
Browser:
Resolution
Fixed
Reason Code:
Fixed
Votes:
9
Vote Comments:
I don't want to live in a world where the string '0,6' is equal to '6,0'.
Comment by External U.
07/18/2012 18:44:50 GMT
Seriously Adobe needs to STOP using this backwards compatibility issue to not fix bugs which can cause REAL ISSUES for developers in their applications.
Comment by External U.
02/21/2014 17:17:00 GMT
Agree with Mary Jo and Mike
Comment by External U.
02/24/2014 12:56:56 GMT
I believe that a language ought do what it says it does, and have a certain amount of grounding in reality. That is, if I say I am testing for an integer, I ought expect that an integer will pass, and a non-integer fail.
Comment by External U.
10/09/2014 16:47:54 GMT
Ugh. Please stop trying to out think us poor developers.
Comment by External U.
10/24/2014 18:05:23 GMT
+1 - I have no use for treating 0,6 (example) as a date
Comment by External U.
11/24/2014 06:04:40 GMT
+1 ...........................................................
Comment by External U.
06/30/2015 04:25:35 GMT
See also : (1,875 lt 80) == true http://trycf.com/scratch-pad/gist/548c4ee5d2a617e4e88e Instead it should throw an error, or treat the left hand side as 1875 (the number) in the sort of comparison.
Comment by External U.
06/30/2015 04:27:27 GMT
+1
Comment by External U.
10/13/2016 09:42:58 GMT