In article <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> wrote: >"J.J.Bailey" <[EMAIL PROTECTED]> wrote: >> x99_sync.c doesn't compile because PATH_MAX isn't defined. PATH_MAX >> isn't defined because this test in limits.h fails: > > PATH_MAX should *not* be used anywhere in the source. It's not >really needed, and POSIX says it's recommended, not required.
Yes but that recommendation was aimed at OS developers, not endusers. For endusers it's "if it is defined, use it. If it's NOT defined, DON'T use it". > i.e. GNU Hurd doesn't define PATH_MAX at *all*. Yes but you still need it for, for example, getcwd(buf, len). The hurd has solved this by a GNU extension - if buf == NULL getcwd() will malloc the needed amount of space itself, but that's not POSIX. Mike. -- "Only two things are infinite, the universe and human stupidity, and I'm not sure about the former" -- Albert Einstein. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
