This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin 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: HEADSUP: cygserver now has MSG, SEM and SHM support


On Sat, Nov 29, 2003 at 11:21:01AM -0500, Nicholas Wourms wrote:
>   In this respect, I think compatibility should 
> trump strict adherence to the SuSv3.  Perhaps the right approach to 
> dealing with nonstandard stuff in the headers would be to use 
> _POSIX_C_SOURCE #if's, i.e.:
> #if _POSIX_C_SOURCE < 200112L
> non-standard code...
> #endif

Could you be a bit more specific about what is wrong or missing from
your point of view?

> Also, I noticed that there are some structures which have gone missing 
> in the new sys/msg.h.  The msgbuf structure, in particular, has not 
> resurfaced, even though it is used by BSD and GNU.  IIRC, I believe 
> FreeBSD defines this in a different header.  Now I realize standards are 
> *good*, but perhaps we could relax the strictness to provide greater 
> compatibility?

Ok, the struct msgbuf is defined in Linux but it's only defined if 
__USE_GNU is given, which isn't by default.  If you like we can add
the struct but only with an appropriate #ifdef as in Linux.  It's
pretty clear from SUSv3 that the struct must be defined by the
application itself and the definition in sys/msg.h is only a *template*.

Anything else?  Please keep in mind that all the stuff which is guarded
by _KERNEL is either only for usage in the internal implementation or
by ipcs.  Since we have our own ipcs, there's no reason to chnage this
to be backward compatible with cygipc's ipcs.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.


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