bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #63509] ctime(3) is obsolescent


From: Bjarni Ingi Gislason
Subject: [bug #63509] ctime(3) is obsolescent
Date: Sun, 11 Dec 2022 17:38:48 -0500 (EST)

URL:
  <https://savannah.gnu.org/bugs/?63509>

                 Summary: ctime(3) is obsolescent
                 Project: GNU troff
               Submitter: bjarniig
               Submitted: Sun 11 Dec 2022 10:38:46 PM UTC
                Category: General
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Sun 11 Dec 2022 10:38:46 PM UTC By: Bjarni Ingi Gislason <bjarniig>
Subject: ctime(3) is obsolescent

See ctime(3) (POSIX.1-2008) and
www.open-std.org/JTC1/SC22/WG14/www/docs/n3047.pdf.

  Used in 

devices/grohtml/grohtml.1.man:.MR ctime 3
devices/grohtml/post-html.cpp:    .put_string(ctime(&t), strlen(ctime(&t))-1)
devices/grohtml/post-html.cpp:      .put_string(ctime(&t),
strlen(ctime(&t))-1)
devices/grops/grops.1.man:.MR ctime 3
devices/grops/ps.cpp:    fputs(ctime(&t), out.get_file());
roff/groff/groff.1.man:.MR ctime 3
roff/troff/troff.1.man:.MR ctime 3

  The mentioning of "ctime(3)" in man pages ("SOURCE_DATE_EPOCH") is
irrelevant (implementation detail which can change and thus cause lost
time by updating that).








    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63509>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]