mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH] add _DIRENT_HAVE_D_* constants to dirent.h
Date: Thu, 14 Jan 2016 17:44:49 -0500	[thread overview]
Message-ID: <20160114224449.GX238@brightrain.aerifal.cx> (raw)
In-Reply-To: <20160113180919.GA11433@nyan>

On Wed, Jan 13, 2016 at 07:09:19PM +0100, Felix Janda wrote:
> they can be used for checking existence of non-standard fields of
> struct dirent, are used by various programs to avoid configure
> checks and are at least present on glibc, uclibc, dietlibc and
> newlib.
> ---
> The motivation for this patch is
> 
> http://oss.sgi.com/archives/xfs/2016-01/msg00388.html
> ---
>  include/dirent.h | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/include/dirent.h b/include/dirent.h
> index 5aa8510..b2ffe8a 100644
> --- a/include/dirent.h
> +++ b/include/dirent.h
> @@ -57,6 +57,9 @@ int getdents(int, struct dirent *, size_t);
>  #endif
>  
>  #ifdef _GNU_SOURCE
> +#define _DIRENT_HAVE_D_OFF
> +#define _DIRENT_HAVE_D_RECLEN
> +#define _DIRENT_HAVE_D_TYPE
>  int versionsort(const struct dirent **, const struct dirent **);
>  #endif

I like the concept of defining macros to publish the availability of
extensions like this, but I don't think they should be dependent on
_GNU_SOURCE. At the very least they should also be available under
_DEFAULT_SOURCE (_BSD_SOURCE), but since they're in the reserved
namespace (underscore followed by capital) I'd prefer to have them
exposed unconditionally.

I'm also skeptical of whether d_off and d_reclen should be promoted as
public APIs. They don't seem to be useful (unlike d_type which is
highly useful) and may lock down some assumptions about
implementation.

Rich


  reply	other threads:[~2016-01-14 22:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 18:09 Felix Janda
2016-01-14 22:44 ` Rich Felker [this message]
2016-01-15  2:27   ` Rich Felker
2016-01-15 16:20     ` Felix Janda

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=20160114224449.GX238@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /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/musl/

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).