Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Dec 2003 11:57:45 -0800
From:      "Jordan K. Hubbard" <jkh@queasyweasel.com>
To:        "Jacques A. Vidrine" <nectar@FreeBSD.org>
Cc:        cvs-src@FreeBSD.org
Subject:   Re: cvs commit: src/include fnmatch.h
Message-ID:  <483CA6BC-30CB-11D8-AAAC-000393BB9222@queasyweasel.com>
In-Reply-To: <20031217140201.GB6018@madman.celabo.org>
References:  <200312170256.hBH2uSOn062945@repoman.freebsd.org> <200312170254.hBH2sTJx062816@repoman.freebsd.org> <20031217132252.GA6018@madman.celabo.org> <20031217133953.GD60229@elvis.mu.org> <20031217140201.GB6018@madman.celabo.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--Apple-Mail-6-1042068765
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed


On Dec 17, 2003, at 6:02 AM, Jacques A. Vidrine wrote:

> The only reason I brought it up is because the absence of FNM_NOSYS on
> BSD for the past decade apparently hasn't been noticed until now (why
> now?), seeming to imply that there aren't any such applications.

Glad you asked.  It's basically my intention to bring FreeBSD's headers 
and libraries as close to conformance to Unix03 as I can over the next 
few months (years?), some of which will actually have a demonstrable 
effect on FreeBSD's portability (the change to *index.c being a case in 
point - someone actually noticed the aberrant behavior in a user 
application) and some of which will be largely in the eye-rolling 
"whatever!" category, where it's hard to imagine any justification 
other than "the standard calls for it."   That said, there will still 
be cases where the latter changes morph into the former at various 
points in the future simply because it is part of the standard and 
people tend to code to it.  Given that it's hard to tell the difference 
in advance, we might just as well take each and every change necessary 
for conformance.  Should "FreeBSD" ever pursue actual Unix 
certification, not that I'm advocating for or against this in any way, 
these changes will also ease the pain of doing so.  Finally, it's never 
been bad for marketing to be able to say that "FreeBSD largely conforms 
to the foo standard" on the back of the CDs. :-)

--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer

--Apple-Mail-6-1042068765--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?483CA6BC-30CB-11D8-AAAC-000393BB9222>