From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: gethostname max len
Date: Mon, 22 Mar 2004 11:02:55 +1000 [thread overview]
Message-ID: <87fzc1n16o.fsf@zip.com.au> (raw)
In-Reply-To: <20040322010510.GA235@gmx.de> (Wolfgang Jaehrling's message of "Mon, 22 Mar 2004 02:05:11 +0100")
Wolfgang Jaehrling <pro-linux@gmx.de> writes:
>
> Which is what Guile probably also should do, otherwise it won't work
> correctly on the GNU system, which has no limit on the length of host
> names;
Oh, is that how the -1 is to be understood? Nosing around the glibc
sources it looked only like it didn't have an implementation for
HOST_NAME_MAX yet.
> the current code that checks for ENAMETOOLONG looks quite
> GNU/Linux-specific.
Yep. (I'm not proposing to change that, only to get a better first
size for the buffer.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-03-22 1:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-21 22:22 gethostname max len Kevin Ryde
2004-03-22 1:05 ` Wolfgang Jaehrling
2004-03-22 1:02 ` Kevin Ryde [this message]
2004-03-22 1:34 ` Wolfgang Jaehrling
-- strict thread matches above, loose matches on Subject: below --
2004-03-26 14:47 Nelson H. F. Beebe
2004-03-27 22:48 ` Kevin Ryde
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fzc1n16o.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@gnu.org \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).