Nah, you ought to change it to eight years, to match the 8 in java 8, and then replace the reference to Sytem.currentTimeMillis with an abstract time factory so that any user can redefine year length as a class and so that anyone who knows which web site to visit can follow the clear instructions to subscribe and pay big bucks and make it "just work".
(I'm only 90% sarcastic here. And, with that, I'm going to go back to lurking.) Thanks, -- Raul On Wed, Dec 31, 2014 at 4:16 AM, Ted Unangst <[email protected]> wrote: > On Wed, Dec 31, 2014 at 02:23, Stuart Henderson wrote: >> On 2014/12/31 00:13, Marc Espie wrote: >>> well, jdk 1.7 just stopped building. because one file is >10 years old and >>> there is an explicit check for that in the build process. >>> >>> Just think about it. >> >> Can't go perpetuating 10-year-old currencies, that would be terrible! >> >> This should be reasonable until openjdk catches up with the newer files >> from java 8. >> +- if (Math.abs(time - System.currentTimeMillis()) > ((long) >> 10) * 365 * 24 * 60 * 60 * 1000) { >> +- throw new RuntimeException("time is more than 10 years >> from present: " + time); >> +- } > > Maybe we should only change it to eleven years? Kind of like how > the government does "emergency" budget extensions? /ducks and runs... >
