*common year*
.
(*i will be ‘115’* by then…)
“by god! you’re right!”
(going on ‘116’)
(if i make it that far)
(the next ‘century year’ exception)
(as this year is incorrectly assumed to be a ‘leap year’ because it is divisible by ‘4’)
(remember that every ‘century year’ (with the exception of every ‘4th century year’ is a ‘common year’)
(NOT A ‘LEAP YEAR’!)
(according to the ‘gregorian calendar’)
.
*YEAR 2100 PROBLEM*
*WIKI-LINK*
(‘DOS’ + ‘windows’ file date ‘API’ and ‘conversion functions’ (such as ‘INT 21h/AH=2Ah’) officially support dates up to ‘2099-12-31 only’ (even though the underlying ‘FAT filesystem’ would theoretically support dates up to ‘2107’))
(hence, ‘DOS-based operating systems’ as well as ‘applications’ that convert other formats to the ‘FAT/DOS format’, may show unexpected behavior starting ‘2100-01-01’)
.
(another problem will emerge at the end of ‘2100-02-28’…)
(since ‘2100’ is not a ‘leap year’)
(…whereas many common implementations of the ‘leap year algorithm’ are ‘incomplete’ or ‘simplified’, and thus will erroneously assume it to be a ‘leap year’)
(this would cause the ‘date’ to incorrectly ‘roll over’ from ‘2100-02-28’ to ‘2100-02-29’…)
(instead of directly to ‘2100-03-01’)
(why didn’t ‘we’ think of this when ‘we’ created these programs?)
.
.
👈👈👈 ☜ *-YEAR 2099-*
.
*-YEAR 2101-* ☞ 👉👉👉
.
.
👈👈👈☜*“FUTURE COMMON YEARS”* ☞ 👉👉👉
.
.
💕💝💖💓🖤💙🖤💙🖤💙🖤❤️💚💛🧡❣️💞💔💘❣️🧡💛💚❤️🖤💜🖤💙🖤💙🖤💗💖💝💘
.
.
*🌈✨ *TABLE OF CONTENTS* ✨🌷*
.
.
🔥🔥🔥🔥🔥🔥*we won the war* 🔥🔥🔥🔥🔥🔥