From: "Bill Schottstaedt" <bil@ccrma.Stanford.EDU>
Cc: guile-devel@gnu.org
Subject: Re: Guile 1.7.91 has been released.
Date: Mon, 13 Feb 2006 14:33:37 -0800 [thread overview]
Message-ID: <20060213223050.M63331@ccrma.Stanford.EDU> (raw)
In-Reply-To: <87wtfzrlfp.fsf@zip.com.au>
I don't think NAME_MAX is defined anywhere -- the documentation says
you should use pathconf instead. Here's the portion of limits.h where
they commented out NAME_MAX:
/*
* POSIX 1003.1a, section 2.9.5, table 2-5 contains [NAME_MAX] and the
* related text states:
*
* A definition of one of the values from Table 2-5 shall be omitted from the
* <limits.h> on specific implementations where the corresponding value is
* equal to or greater than the stated minimum, but where the value can vary
* depending on the file to which it is applied. The actual value supported for
* a specific pathname shall be provided by the pathconf() (5.7.1) function.
*
* This is clear that any machine supporting multiple file system types
* and/or a network can not include this define, regardless of protection
* by the _POSIX_SOURCE and _POSIX_C_SOURCE flags.
*
* #define NAME_MAX 14
*/
I'd be happy to test anything, of course. (The d_name field is still defined
to be 1 char long, so I think the glibc comment still pertains to Solaris,
but I'm really no expert about this system!).
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-02-13 22:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 23:15 Guile 1.7.91 has been released Marius Vollmer
2006-02-12 23:46 ` Michael Tuexen
2006-02-14 21:50 ` Marius Vollmer
2006-02-18 23:45 ` Han-Wen Nienhuys
2006-02-20 20:59 ` Marius Vollmer
2006-02-13 8:37 ` Han-Wen Nienhuys
2006-02-13 9:41 ` Ludovic Courtès
2006-02-13 19:50 ` Marius Vollmer
2006-02-14 9:22 ` Ludovic Courtès
2006-02-14 19:39 ` Marius Vollmer
2006-02-13 12:49 ` Bill Schottstaedt
2006-02-13 21:35 ` Kevin Ryde
2006-02-13 22:33 ` Bill Schottstaedt [this message]
2006-02-13 22:50 ` Kevin Ryde
2006-02-13 23:35 ` Bill Schottstaedt
2006-02-14 0:58 ` Kevin Ryde
2006-02-14 1:28 ` Kevin Ryde
2006-02-14 21:36 ` Bill Schottstaedt
2006-02-15 0:03 ` Kevin Ryde
2006-02-15 7:56 ` Ludovic Courtès
2006-02-15 12:37 ` Guile 1.7.91 has been released (x86-64 segfault) Bill Schottstaedt
2006-02-14 9:27 ` Guile 1.7.91 has been released Ludovic Courtès
2006-02-13 15:31 ` Bill Schottstaedt
2006-02-14 8:50 ` Andy Wingo
2006-02-20 18:36 ` Neil Jerram
2006-02-20 20:04 ` Bill Schottstaedt
2006-02-13 18:40 ` Bill Schottstaedt
2006-02-14 11:35 ` Han-Wen Nienhuys
2006-02-14 21:32 ` Marius Vollmer
2006-02-14 13:58 ` Ludovic Courtès
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=20060213223050.M63331@ccrma.Stanford.EDU \
--to=bil@ccrma.stanford.edu \
--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).