From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: *
X-Spam-Status: No, score=1.3 required=5.0 tests=BAYES_00,INVALID_MSGID,
	MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,bd45e29f9dafca87
X-Google-Attributes: gid103376,public
From: Ted Dennison <dennison@telepath.com>
Subject: Re: bitwise comparators
Date: 2000/01/18
Message-ID: <86214l$9uo$1@nnrp1.deja.com>#1/1
X-Deja-AN: 574225175
References: <3880D375.7E363123@hotmail.com> <38829638.0@news.pacifier.com>
 <3882FC1C.2BA8C959@hotmail.com> <85vmn2$ki1$1@nnrp1.deja.com>
 <38836CF2.AB738B8B@hotmail.com> <388394E0.55D1E913@maths.unine.ch>
X-Http-Proxy: 1.0 x30.deja.com:80 (Squid/1.1.22) for client 204.48.27.130
Organization: Deja.com - Before you buy.
X-Article-Creation-Date: Tue Jan 18 15:33:42 2000 GMT
X-MyDeja-Info: XMYDJUIDtedennison
Newsgroups: comp.lang.ada
X-Http-User-Agent: Mozilla/4.6 [en] (WinNT; I)
Date: 2000-01-18T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <388394E0.55D1E913@maths.unine.ch>,
  Gautier <gautier.demontmollin@maths.unine.ch> wrote:
> Alexander Van Hecke wrote:
>
> > C was ment to be used modular and for reuse : put your code in
> > separate .c and .h files.
>
> I feel you miss something. The .h files are just included texts; the
> `defines' in one can influence another so the inclusion order is
> delicate; there is no link (apart a moral one) between the .h and the
> .c and - correct me if I'm wrong - a standard C compiler won't check
> the integrity between .h and .c ... In addition, the most resources on
> the Net break your .h  <-> .c rule...

That's just about the biggest problem in my book. Using ".h" files that
way is just a convention that many C developers follow. There's no teeth
to it, and there are many other ways the include feature can be
(ab)used. For instance, I've seen several C systems where included
files have no extention (".h") on them. There are even several places in
the vxWorks kernel source code where ".c" files are #include'd. I can be
indignant that the developers would do such a thing to poor unsuspecting
readers like myself, but its perfectly legal (and running) C.

--
T.E.D.

http://www.telepath.com/~dennison/Ted/TED.html


Sent via Deja.com http://www.deja.com/
Before you buy.