Today I was rewriting a function. The function makes an HTTP request with a form-encoded request body. But after preparing the body of the reqeust,...
For further actions, you may consider blocking this person and/or reporting abuse
There is a bug in Excel that results in incorrect leap year calculations. The bug was originally introduced in Lotus 123 and Microsoft intentionally copied the bug so as to be able to claim compatibility. Go figure....
The bug is that centuries should NOT be leap years even though they are divisible by 4 UNLESS they are also a millennium. 1896, 1904, 1996, 2000 and 2004 are leap years. 1900 was not. Fortunately for me it is unlikely to significantly impact my work in the run up to 2100.