Clive D. W. Feather wrote, with respect to conversion between JDN and Gregorian calendar date,
> >So in order to calculate the >> actual date where the drift adjustment occurs you have to face a very > >elaborate conversion. >No, you need to use a library that's already been written to do the job. >Takes 10 seconds or so. To make people comfortable with your work, you need to state the earliest and latest date For which your code works correctly. If your organization is strict, you might even be required to test inputs to be sure they are in the domain of the function. I have found that many published algorithms fail to state the earliest and latest date for which they work. Finding out will require much more than 10 seconds. Of course the code has to be tested. A list of known-good conversions should be easy to find for contemporary dates. Although not needed for the purpose of leap seconds, does anyone know a known-good conversion list that includes ancient dates and dates far in the future? Gerard Ashton _______________________________________________ LEAPSECS mailing list LEAPSECS@leapsecond.com https://pairlist6.pair.net/mailman/listinfo/leapsecs