cvs commit: src/include fnmatch.h

[Jacques A. Vidrine]

On Wed, Dec 17, 2003 at 05:39:53AM -0800, Alfred Perlstein wrote:
> It is still required for standards conformance.

Yes, you are right.  The SUSv3 `Implementation Conformance' section does
not indicate that `obsolescent' features need be present, but buried in
the `Rationale for Base Definitions' under `Terminology' is

``The terms "legacy" and "obsolescent" are different: a feature marked
  LEGACY is not recommended for new work and need not be present on an
  implementation (if the XSI Legacy Option Group is not supported).
  __A_feature_noted_as_obsolescent_is_supported_by_all_implementations__,
  but may be removed in a future revision; new applications should not
  use these features.'' (emphasis added) (quoted for the other curious)

This seems to be the only place in all of SUSv3 to indicate
that `obsolescent' features must be supported by a conforming
implementation.  I was under a different impression previously.

> There may be tools out there that expect to "just work" like so
> 
> switch (id) {
> ...
> case FNM_NOSYS:
>   str = "FNM_NOSYS";
> ...
> }
> 
> and those should "just work".

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.

Cheers,
-- 
Jacques Vidrine   NTT/Verio SME      FreeBSD UNIX       Heimdal
nectar at celabo.org jvidrine at verio.net nectar at freebsd.org nectar at kth.se