Welcome to the NavList Message Boards.


A Community Devoted to the Preservation and Practice of Celestial Navigation and Other Methods of Traditional Wayfinding

Compose Your Message

Add Images & Files
    Re: Leap second on December 31
    From: Bob Goethe
    Date: 2016 Dec 29, 10:48 -0800

    >>As long as the rules are simple and clearly stated, there is no problem.<<

    I agree with this wholeheartedly, Frank.  But it works out differently for me in practice than it does in your ideal solution.  I include a small table of leap seconds stored in my application which I check for time related functions.  The time required to check this table is too small for me to clock; that is, it is less than 1 ms.  I write a time-function (which checks this table) once, refer to it thereafter, and update the table whenever another leap second is inserted.

    If my customer cuts me off and doesn't replace me with another programmer, then their table fails to get updated, and the time in their application becomes inaccurate.  I am sufficiently mercinary to see this as a feature rather than a bug.


    Browse Files

    Drop Files


    What is NavList?

    Join NavList

    (please, no nicknames or handles)
    Do you want to receive all group messages by email?
    Yes No

    You can also join by posting. Your first on-topic post automatically makes you a member.

    Posting Code

    Enter the email address associated with your NavList messages. Your posting code will be emailed to you immediately.

    Email Settings

    Posting Code:

    Custom Index

    Start date: (yyyymm dd)
    End date: (yyyymm dd)

    Visit this site
    Visit this site
    Visit this site
    Visit this site
    Visit this site
    Visit this site