On 2016-03-07 14:03, admin@??? wrote:
> https://bugs.exim.org/show_bug.cgi?id=1805
>
> --- Comment #6 from Heiko Schlittermann <hs@???> ---
> (In reply to Todd Rinaldo from comment #5)
>> OSX seems to support this just fine. What are we worried about not
>> supporting it?
>>
>> GETCWD(3) BSD Library Functions Manual
>> GETCWD(3)
>>
>> NAME
>> getcwd, getwd -- get working directory pathname
>> ...
>> If buf is NULL, space is allocated as necessary to store the
>> pathname.
>> This space may later be free(3)'d.
>
> We still support some ancient *BSD systems. (I didn't know about that
> until
> last week. It was that, what the public release delayed.)
>
> I think, I'll go the big_buffer route, but I've to check the usage of
> the
> buffer. And I've to run it through the testsuite. So it may take it
> bit.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
This is true on FreeBSD 10.3 (I don't know how far back, but the date on
the manual page
is April of 2010.
GETCWD(3) FreeBSD Library Functions Manual
GETCWD(3)
NAME
getcwd, getwd -- get working directory pathname
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <unistd.h>
char *
getcwd(char *buf, size_t size);
char *
getwd(char *buf);
DESCRIPTION
The getcwd() function copies the absolute pathname of the current
working
directory into the memory referenced by buf and returns a pointer
to buf.
The size argument is the size, in bytes, of the array referenced by
buf.
If buf is NULL, space is allocated as necessary to store the
pathname.
This space may later be free(3)'d.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: ler@???
US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961
