From owner-freebsd-bugs Wed Jan 24 10: 0:22 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0BAB237B401 for ; Wed, 24 Jan 2001 10:00:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0OI04b66577; Wed, 24 Jan 2001 10:00:05 -0800 (PST) (envelope-from gnats) Date: Wed, 24 Jan 2001 10:00:05 -0800 (PST) Message-Id: <200101241800.f0OI04b66577@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Garrett Wollman Subject: misc/24590: timezone function not compatible witn Single Unix Spec v2 Reply-To: Garrett Wollman Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/24590; it has been noted by GNATS. From: Garrett Wollman To: crandall@matchlogic.com Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: misc/24590: timezone function not compatible witn Single Unix Spec v2 Date: Wed, 24 Jan 2001 12:52:34 -0500 (EST) < I realize that I can work around this in an application a number > of ways. For example, use FreeBSD's tm_gmtoff member of struct tm. > However, is it a long-term goal for FreeBSD to conform to the > Single Unix Specification? It is a long-term goal for FreeBSD to conform to POSIX and include as much Single UNIX Spec (aka XSI) functionality as seems useful and prudent. We are not likely to change the API in the way that you suggest, precisely because superior alternatives exist, and changing to the XSI definition would break backward compatibility. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message