[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.20.1602292308370.14767@monopod.intra.ispras.ru>
Date: Mon, 29 Feb 2016 23:10:51 +0300 (MSK)
From: Alexander Monakov <amonakov@...ras.ru>
To: musl@...ts.openwall.com
Subject: Re: [PATCH] add sched_getcpu
On Mon, 29 Feb 2016, Rich Felker wrote:
> > > Policy is to always include the header with the public declaration
> > > (and any feature test macros necessary to get it) so that the compiler
> > > checks the implementation against the public declaration.
> >
> > This policy certain makes sense; I pointed that out because I've seen it
> > violated; at least the following files violate it by defining something
> > without including anything:
[snip]
> > src/internal/procfdname.c
>
> This is an internal function.
Please explain the difference in policy for internal functions. The original
motivation (compiler checking the prototype) sounds like it's valuable for
internal functions too.
Thanks.
Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
