Warranted not to forget, there can be no safety. And that's not going to happen.

Now, what about Proclub? Is Proclub "Year 2000 Compliant''? The answer is that Proclub is every bit as Y2K compliant as is your pencil; no more, and no less. Does that comfort you? It shouldn't. Just as you can commit Y2K transgressions with your pencil, so too you can do so with Proclub -- or with any other tool, for that matter.

The date and time functions supplied with Proclub are derived from their namesakes from the programming language. These supply adequate information to determine the year well beyond 2000. 2038 is when trouble strikes, but only for those of us still stuck on 32-bit machines, a somewhat unlikely albeit admittedly not entirely unthinkable situation.

The year returned is, contrary to popular misconception, not by definition a two-digit year. Rather, it merely happens to be such right now. What it actually is, is the current year minus one thousand nine hundred. For years between 1900 and 1999 this happens to be a 2-digit decimal number, but that's not going to last long.

To avoid the year 2000 problem, simply do not treat the year as a number. Easy to say, and easy to break. Imagine that you want find out what the year appears to be in five years. You write code like this:

Warranted not to forget, there can be no safety. And that's not going to happen.