This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH 09/22] Provide cap_rights_t via <sys/types.h>

From: Corinna Vinschen <vinschen at redhat dot com>
To: newlib at sourceware dot org
Date: Wed, 20 Apr 2016 10:49:29 +0200
Subject: Re: [PATCH 09/22] Provide cap_rights_t via <sys/types.h>
Authentication-results: sourceware.org; auth=none
References: <1460986182-11952-1-git-send-email-sebastian dot huber at embedded-brains dot de> <1460986182-11952-10-git-send-email-sebastian dot huber at embedded-brains dot de>
Reply-to: newlib at sourceware dot org

Hi Sebastian,

On Apr 18 15:29, Sebastian Huber wrote:
> Provide cap_rights_t via <sys/types.h> if __BSD_VISIBLE for BSD
> compatibility.

Do we really want to clutter the namespace with all these very
FreeBSD-centric types?  I'm mostly concerned about this struct
cap_rights, but also many of the other types are rather... uncommon.
I checked their existence on OpenBSD, NetBSD, and Linux, and none of
them define those:

  addr_t
  accmode_t
  cap_rights/cap_rights_t
  c_caddr_t
  cpulevel_t
  cpusetid_t
  cpuwhich_t
  uintfptr_t
  vm_offset_t
  vm_size_t
  vm_ooffset_t
  vm_paddr_t
  vm_pindex_t

addr_t, vm_offset_t, and vm_size_t are defined in Cygwin, but still,
do we really want them available generically?  __BSD_VISIBLE is set
by default...

Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
Red Hat

Attachment: signature.asc
Description: PGP signature

Follow-Ups:
- Re: [PATCH 09/22] Provide cap_rights_t via <sys/types.h>
  - From: Sebastian Huber

References:
- More FreeBSD compatiblity
  - From: Sebastian Huber
- [PATCH 09/22] Provide cap_rights_t via <sys/types.h>
  - From: Sebastian Huber

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]