DateToStr and Delphi XE2

Question

I upgraded one project from XE to XE2 and I noticed that DateToStr doesn't work exactly as before.

If I try to covert a null date to str it gives "Invalid floating point operation". While this was not there in XE.

Why there is this difference? Are there similar behaviours for other functions? (I mean some function that in a similar case = converting a null value changes the behaviour)

Perhaps this is what you are referring to: http://stackoverflow.com/questions/9255337/delphi-xe2-formatdatetime-passing-693594 — David Heffernan, Mar 06 '12 at 14:09
Can you show some code? Passing an uninitialized TDateTime just returns 30/12/1899 on my machine. — pritaeas, Mar 06 '12 at 14:22
@pritaeas You mean passing a `TDateTime` that has value of `0.0`. — David Heffernan, Mar 06 '12 at 14:22
@pritaeas Probably not because a value of `0.0` does not throw an FP error — David Heffernan, Mar 06 '12 at 14:37
@DavidHeffernan yes it is the same as http://stackoverflow.com/questions/9255337/delphi-xe2-formatdatetime-passing-693594 does anyone know if this has been solved in Update 4? — UnDiUdin, Mar 08 '12 at 09:06
I believe that this change is not going to be solved. This change is by design. — David Heffernan, Mar 08 '12 at 09:09

score 1 · Accepted Answer · answered Mar 14 '12 at 09:56

After investigating I realized that this design choice made by Embarcadero in XE2 will affect a lot of old code. Wherever possible I replaced DateTimeToStr or I added checks for NULL dates before trying to convert to string.

Also DevExpress have some problems with their components because of this issue.

DateToStr and Delphi XE2

1 Answers1