Re: LC Date Conversions post 2035

2022-11-09 Thread Bob Sneidar via use-livecode
Probably based on Unix... ;-) Bob S On Nov 7, 2022, at 06:55 , Martin Koob via use-livecode mailto:use-livecode@lists.runrev.com>> wrote: Not sure what Window is doing that it is only going to work till 3000. Maybe MicroSoft have decided to EOL Windows then and have plans to release a

RE: LC Date Conversions post 2035 [OT ish]

2022-11-07 Thread Ralph DiMola via use-livecode
runrev.com] On Behalf Of Mark Clark via use-livecode Sent: Sunday, December 31, 2034 9:25 PM To: How to use LiveCode Cc: Mark Clark Subject: LC Date Conversions post 2035 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

Re: LC Date Conversions post 2035

2022-11-07 Thread Paul Dupuis via use-livecode
The results on Windows may also depend upon whether you built a 32 bit standalone or a 64 bit standalone? Or using the 32 or 64 bit version of whatever release of Livecode is being used. On 11/7/2022 9:55 AM, Martin Koob via use-livecode wrote: Hi This thread reminded me of some sci-fi show

Re: LC Date Conversions post 2035

2022-11-07 Thread Martin Koob via use-livecode
Hi This thread reminded me of some sci-fi show show I was watching which referenced the collapse of society on earth caused by a bug around 2035 or something like that where the computers could not process dates beyond that. I thought this is just a off hand reference to something Y2K. But

Re: LC Date Conversions post 2035

2022-11-07 Thread Mark Clark via use-livecode
Thanks for the quick responses. In this case I did indeed use a 4 digit year as initial input (always), but still managed to shoot myself with a second conversion step. Converted my nicely formed input text to dateitems -- all good. Did my addition for renewal days to item 3. Check. Then I

Re: LC Date Conversions post 2035

2022-11-06 Thread Andreas Bergendal via use-livecode
Had to test this out of curiosity. Indeed, when using 2-digit year, that is the result, as expected and explained in the dictionary entry for centuryCutoff. But how far does the 4-digit conversion work? Here’s what I’ve found: - On Windows 10, it works until year 3000, and stops working on year

Re: LC Date Conversions post 2035

2022-11-06 Thread J. Landman Gay via use-livecode
That's the centuryCutoff in action, but I think something is amiss since it's only supposed to apply to 2-digit years and 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

Re: LC Date Conversions post 2035

2022-11-06 Thread J. Landman Gay via use-livecode
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

LC Date Conversions post 2035

2022-11-06 Thread Mark Clark via use-livecode
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