Date: Mon, 9 Nov 2009 11:31:06 -0500 From: Garrett Wollman <wollman@csail.mit.edu> To: "Joseph S. Atkinson" <jsa.bsd@gmail.com> Cc: freebsd-standards@freebsd.org Subject: timezone: long vs char* Message-ID: <19192.17354.890527.943635@khavrinen.csail.mit.edu> In-Reply-To: <4AF7651F.20703@gmail.com> References: <4AF7651F.20703@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Sun, 08 Nov 2009 19:41:03 -0500, "Joseph S. Atkinson" <jsa.bsd@gmail.com> said: > Hello. I was working on bringing audio/liboggz up to date in ports, but hit a > snag. liboggz expects timezone information to be long, which is (I am told) in > accordance with SUSv3. FreeBSD is appears to be returning char*. > I asked about this in #bsdports and was told that it appears that FreeBSD is > wrong in this case and should be fixed. I saw no mention of this as a known > issue on the standards webpage. I think the people on "#bsdports" (an IRC channel, I assume) are wrong. FreeBSD has never targeted conformance to any version of SUS, which memorializes a large number of UNIX System V's historic mistakes. We do target conformance to POSIX (IEEE Std. 1003.1-2008 is the current version). In the POSIX specification, the declarations of "timezone" and "daylight" in <time.h> are flagged as "XSI", meaning that they are part of the X/Open System Interfaces extension, which in turn means that they are part of SUS but not POSIX. -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19192.17354.890527.943635>