Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #103759

Re: Private and public code

Path csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From GOTHIER Nathan <nathan.gothier@gmail.com>
Newsgroups comp.lang.c
Subject Re: Private and public code
Date Sun, 12 Feb 2017 21:38:45 +0100
Organization A noiseless patient Spider
Lines 28
Message-ID <20170212213845.24b28c8a15ee4e41cfe2e07f@gmail.com> (permalink)
References <20170212200353.005eb833d8a8d4e8e6d8f3de@gmail.com> <egbq9cFbmb2U3@mid.individual.net>
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
Injection-Info mx02.eternal-september.org; posting-host="d6237fe960ddbbbb1d8cbb22de58142f"; logging-data="7853"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+LW3WZ5oHf+V1mXKR2FlCAhqJCy8CmwQo="
X-Newsreader Sylpheed 3.2.0 (GTK+ 2.24.20; x86_64-slackware-linux-gnu)
Cancel-Lock sha1:0Cdz7/tlHHdQ4hzlPDY1HarRSls=
Xref csiph.com comp.lang.c:103759

Show key headers only | View raw

On Mon, 13 Feb 2017 08:10:36 +1300
Ian Collins <ian-news@hotmail.com> wrote:

> On 02/13/17 08:03 AM, GOTHIER Nathan wrote:
> 
> Please limit your line length!
> 
> > Hello everybody,
> >
> > After reading many headers in different C projects, I realized the
> > fact that there are many private code (macros, typedefs, ...)
> > included in headers that makes difficult to distinguish what is
> > useful for the end user.
> >
> > Since I consider headers as some kind of minimal documentation for C
> > programmers, I put every private code in source files and only public
> > code in headers. Although it could lead sometimes to put all
> > unrelated private code in one common source file with an include
> > guard.
> >
> > What do you think about this practice?
> 
> Why don't you just use a private header?
> 
> -- 
> Ian

Do you compile private headers? For me appending "private" to "header" looks weird... since we usually make public access to private code with headers. ;-)

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Private and public code GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-02-12 20:03 +0100
  Re: Private and public code Ian Collins <ian-news@hotmail.com> - 2017-02-13 08:10 +1300
    Re: Private and public code GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-02-12 21:38 +0100
      Re: Private and public code Richard Heathfield <rjh@cpax.org.uk> - 2017-02-12 20:58 +0000
        Re: Private and public code GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-02-12 23:06 +0100
          Re: Private and public code Richard Heathfield <rjh@cpax.org.uk> - 2017-02-13 06:00 +0000
            Re: Private and public code GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-02-13 08:31 +0100
      Re: Private and public code Ian Collins <ian-news@hotmail.com> - 2017-02-13 19:07 +1300
        Re: Private and public code GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-02-13 09:14 +0100

csiph-web