From owner-freebsd-standards@FreeBSD.ORG Thu Dec 6 00:12:04 2007 Return-Path: Delivered-To: standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44EA316A419 for ; Thu, 6 Dec 2007 00:12:04 +0000 (UTC) (envelope-from matthieu@nxdomain.fr) Received: from homer.epita.info (alice.nxdomain.fr [213.251.160.11]) by mx1.freebsd.org (Postfix) with ESMTP id 112DE13C455 for ; Thu, 6 Dec 2007 00:12:03 +0000 (UTC) (envelope-from matthieu@nxdomain.fr) Received: from [172.16.31.6] (unknown [172.16.31.6]) by homer.epita.info (Postfix) with ESMTP id 3006578D04; Thu, 6 Dec 2007 01:12:02 +0100 (CET) Message-ID: <47573E4F.9070403@nxdomain.fr> Date: Thu, 06 Dec 2007 01:11:59 +0100 From: Matthieu Michaud User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Bruce Evans References: <47559FF0.5090008@nxdomain.fr> <20071205132138.J6892@delplex.bde.org> In-Reply-To: <20071205132138.J6892@delplex.bde.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: standards@freebsd.org Subject: Re: make struct timeval posix compliant ? X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Dec 2007 00:12:04 -0000 Bruce Evans wrote: > On Tue, 4 Dec 2007, Matthieu Michaud wrote: > >> Few months ago I sent a mail to stable@freebsd.org in the hope to >> discuss struct timeval posix conformance in RELENG_6. >> >> http://docs.freebsd.org/cgi/mid.cgi?1397BA88-CC55-4585-86CB-3BD08FBABEF5 >> >> Given the few answers, I may have targetted the wrong mailing list or >> this change has no interest. So, here are the questions again : >> >> - Do you want FreeBSD 6 to conform posix specs for struct timeval ? >> (it's not always a right thing to do to strictly conform standards) > > No, but I don't use FreeBSD-6. > >> - Is it ok to do it ? (if i'm correct there is a minor abi change and >> this could be a strong reason to stay as is) > > It is a huge ABI breakage for arches with 64-bit longs and 32-bit > time_t's (these seem to be only alpha, and i386 and powerpc with the > not-really-supported correctly-sized longs). These could be ifdefed > like arm already is (ugh). > > It is a minor API breakage/fix. > > Bruce This is a little portability issue. I noticed it while working on an app targetting both 6 and 7. I wasn't 100% sure of the consequences. I now am and you're right : this is a minor API fix and a big API break. This is no game to play and I'll live with it. Thanks for your answer.