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


Groups > comp.lang.c > #103751

Private and public code

From GOTHIER Nathan <nathan.gothier@gmail.com>
Newsgroups comp.lang.c
Subject Private and public code
Date 2017-02-12 20:03 +0100
Organization A noiseless patient Spider
Message-ID <20170212200353.005eb833d8a8d4e8e6d8f3de@gmail.com> (permalink)

Show all headers | View raw


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?

Back to comp.lang.c | Previous | Next — 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