That's the centuryCutoff property in action, but it's only supposed to
apply to 2-digit years. So I think something is amiss since you supply a
4-digit year.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On November 6, 2022 8:28:34 PM Mark Clark via use-livecode
<use-livecode@lists.runrev.com> wrote:
I was testing one of the tools I use to handle licensing today and decided
to run the series through a few iterations adding 2 years at a time. I
noticed that my dates were reverting to the 20th c. Hmm, whoops.
After a bit of head scratching I decided it wasn't just my doing.
Date conversion sort of works but the output can lead to trouble in the
future. I've done a few tests and some lengthy, but if anyone cares to
perform the "short test," please do.
Change your date to 12/31/2034; then change to 2035.
run this:
put the date into test
convert test to dateitems
answer item 1 of test --works in 2034; broken in 2035
Mark
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
