From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Reuben Thomas <rrt@sc3d.org>
Subject: Re: NAME_MAX on MingW
Date: Mon, 08 Mar 2021 01:14:15 +0100 [thread overview]
Message-ID: <1841389.BC9EOF7Wat@omega> (raw)
In-Reply-To: <CAOnWdohkuPrPFjcw-hz7LDYqoZS6bph0w0bwhaTVP3UCcxX8dg@mail.gmail.com>
Hi Reuben,
> NAME_MAX is defined in limits.h.
No. POSIX [1] specifies that it may be omitted from <limits.h>, and
that pathconf (_PC_NAME_MAX) is the right way to access the maximum
length of a file name component. [2]
> So my question is: is there something gnulib can/should do here?
I don't see anything Gnulib should do here.
Bruno
[1] https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/limits.h.html
[2] https://pubs.opengroup.org/onlinepubs/9699919799/functions/pathconf.html
next prev parent reply other threads:[~2021-03-08 0:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 23:22 NAME_MAX on MingW Reuben Thomas
2021-03-08 0:14 ` Bruno Haible [this message]
2021-03-08 0:16 ` Reuben Thomas
2021-03-08 9:24 ` Reuben Thomas
2021-03-08 10:06 ` Bruno Haible
2021-03-08 10:12 ` Reuben Thomas
2021-03-08 9:12 ` Reuben Thomas
2021-03-08 9:56 ` Bruno Haible
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1841389.BC9EOF7Wat@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=rrt@sc3d.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).