🚀 go-pugleaf

Top 16 potential FSF responses to the Year 2000 Compliance question:

15) Richard Stallman has predicted that the world will end in 1999.
14) Richard Stallman has predicted that HPUX will end in 1999.
13) Comply with THIS, pal!
12) A Y2K patch is available from Cygnus Support but has not been
    inlcuded in the official distribution due to disagreements over
    implementation.
11) For $100,000 I'll guarantee Year 2000 compliance.
10) GNU g++ is Y2K-compliant when used with the GNU Hurd.  The FSF
    is no longer devoting resources to supporting lesser operating systems.
 9) Use #pragma Y2KCompliant.  Case is important.
 8) Thanks to the power of object-oriented programming, you merely have
    to make all your classes inherit from Compliant::year<2000>
 7) Sorry, we're still working on the year 1991 problem.
 6) The year 2000 is only 3 years away.  We at the FSF do not concern
    ourselves with the near-term.  You and your problems are irrelevant.
 5) The Y2K patch will be distributed under a new version of the GNU
    license that gives us full rights to all code produced by gcc in
    perpetuity.
 4) While ANSI C++ itself is not Y2K compliant, GNU g++ has several non-
    standard extensions that make it compliant.  These extensions are
    enabled via the command-line switch --fenable-year-two-thousand-compliance
 3) We've fixed it for Lignux.  Sorry, what's "aitch peee yewww exxx"?
 2) Y2K compliance is still being finalized by the standards committee;
    the final specification is expected in 2003.
 1) AS OF THIS MORNING THIS IS NOW AN OFFICIAL MICROSOFT VC++ 4.0
    DEVELOPER FORUM.  WE BOUGHT GNU.  ALL OF THEM.  HAVE A NICE DAY.
 0) The year 2000 problem has been solved since gcc 2.4.5.  We are now
    working on the year 4294967296 problem.

---from your friends at the CMU School of Computer Science