All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Excel's Historical Bug: Why 1900 is Incorrectly Treated as a Leap Year

By

susam

2mo ago· 2 min readenNews

Summary

Microsoft Excel incorrectly treats the year 1900 as a leap year due to a historical compatibility decision. This bug originated from Lotus 1-2-3's assumption that 1900 was a leap year, which Microsoft maintained in Excel for backward compatibility. The article explains why this behavior exists and outlines potential issues if the bug were to be corrected, noting that it causes minimal harm to most date calculations.

Key quotes

· 4 pulled
Microsoft Excel incorrectly assumes that the year 1900 is a leap year.
When Lotus 1-2-3 was first released, the program assumed that the year 1900 was a leap year, even though it actually was not a leap year.
This made it easier for the program to handle leap years and caused no harm to almost all date calculations in Lotus 1-2-3.
When Microsoft Multiplan and Microsoft Excel were released, they also assumed that 1900 was a leap year.
Snippet from the RSS feed
Explains why the year 1900 is treated as a leap year in Excel 2000. This article outlines the behaviors that occur if this specific issue is corrected.

You might also wanna read