From: Clint Adams <schizo@debian.org>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: pathconf() again
Date: Fri, 4 Aug 2000 20:52:27 -0400 [thread overview]
Message-ID: <20000804205227.B7925@dman.com> (raw)
In-Reply-To: <000804111549.ZM28988@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Fri, Aug 04, 2000 at 11:15:49AM -0700
> But ... readlink() doesn't have any provision to "read more of the link"
> and doesn't tell you if it truncated what it did read.
I didn't realize that readlink() was so unfriendly. You could
memset() the buffer with 0 and then test to see if the final octet
of the buffer was still zero. If it is, you have a complete,
zero-terminated string. If not, realloc the buffer and try again.
I don't know if that's more or less ugly.
> Only if it's a relative rather than absolute link.
I don't understand the significance.
next prev parent reply other threads:[~2000-08-05 0:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-04 14:53 PATCH: tail-dropping in files module mkdir Clint Adams
2000-08-04 15:17 ` Bart Schaefer
2000-08-04 15:32 ` Clint Adams
2000-08-04 16:10 ` Bart Schaefer
2000-08-05 0:40 ` Clint Adams
2000-08-04 7:02 ` PATCH: pathconf() again Bart Schaefer
2000-08-04 13:19 ` Clint Adams
2000-08-04 18:15 ` Bart Schaefer
2000-08-05 0:52 ` Clint Adams [this message]
2000-08-05 4:48 ` PATCH: tail-dropping in files module mkdir Bart Schaefer
2000-08-07 18:04 ` Clint Adams
2000-08-07 20:39 ` Bart Schaefer
2000-08-08 11:40 ` Clint Adams
2000-08-08 21:47 ` Bart Schaefer
2000-08-09 14:25 ` PATH_MAX vs. _PC_PATH_MAX vs. POSIX (was Re: PATCH: tail-dropping in files module mkdir) Clint Adams
2000-08-09 17:07 ` Bart Schaefer
2000-08-09 17:51 ` Bart Schaefer
2000-08-05 6:45 ` PATCH: pathconf() again Wayne Davison
-- strict thread matches above, loose matches on Subject: below --
2000-08-04 7:06 Sven Wischnowsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000804205227.B7925@dman.com \
--to=schizo@debian.org \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).