I wrote:
...
> Unlike most other getcwd implementations, this one may *potentially*
> return a name that is arbitrarily long (and hence much longer than PATH_MAX).
>
> Currently that doesn't ever happen because the only systems
> that have openat support also have a mostly-working getcwd,
> and *it
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Does the following accurately describe the behaviour of getcwd() in gnulib?
> I'm asking because lib/getcwd.c mentions a certain GNU extension, whereas
> lib/getcwd.h merely refers to the POSIX spec.
>
> /* Get the name of the current working directory, and
Bruno Haible <[EMAIL PROTECTED]> writes:
> Does the following accurately describe the behaviour of getcwd() in gnulib?
> I'm asking because lib/getcwd.c mentions a certain GNU extension, whereas
> lib/getcwd.h merely refers to the POSIX spec.
I think the intent was to implement the GNU extension.
