Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!uunet.UU.NET!sef
From: karish@mindcraft.com (Chuck Karish)
Newsgroups: comp.std.unix
Subject: Re: FILENAME_MAX & _POSIX_PATH_MAX relationship?
Message-ID: <128263@uunet.UU.NET>
Date: 9 Apr 91 23:46:23 GMT
References: <127638@uunet.UU.NET>
Sender: usenet@uunet.UU.NET
Organization: Mindcraft, Inc.
Lines: 19
Approved: sef@uunet.uu.net (Moderator, Sean Eric Fagan - comp.std.unix)
Nntp-Posting-Host: uunet.uu.net
X-Submissions: std-unix@uunet.uu.net
Originator: sef@uunet.UU.NET

Submitted-by: karish@mindcraft.com (Chuck Karish)

In article <127638@uunet.UU.NET> steve@unidata.ucar.edu (Steve Emmerson) writes:
>Would someone who knows please tell me the relationship between the
>Standard C macro FILENAME_MAX and the POSIX macro _POSIX_PATH_MAX.
>
>In particular, should they be the same, or should FILENAME_MAX
>correspond instead to _POSIX_NAME_MAX.

_POSIX_PATH_MAX is more appropriate.  Standard C has no notion of a
path prefix.  Clause 4.9.1 of both the Standard and its rationale
tells us that a buffer of FILENAME_MAX characters should hold
the entire file name (what POSIX.1 would term the 'path').

	Chuck Karish		karish@mindcraft.com
	Mindcraft, Inc.		(415) 323-9000


Volume-Number: Volume 23, Number 26