From:	broeker AT acp3bf DOT knirsch DOT de (Hans-Bernhard Broeker)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: djgpp strangeness
Date:	22 Dec 1999 13:10:56 +0100
Organization:	RWTH Aachen, III. physikalisches Institut B
Lines:	26
Message-ID:	<83qf4g$q8a@acp3bf.knirsch.de>
References:	<tmU74.34$Fc6 DOT 1542 AT weber DOT videotron DOT net>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 945864661 23413 137.226.32.75 (22 Dec 1999 12:11:01 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	22 Dec 1999 12:11:01 GMT
X-Newsreader:	TIN [version 1.2 PL2]
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Valkir (jfd50 AT videotron DOT ca) wrote:
> When I got a bug, sometime, I just put it in /*  */  and then run. After I
> remove then and wow, it work.

> In my prog now, When I add just a header file, (my own) without declaring
> any thing, it doesn't work.

> Once it a while, nothing work anymore. Even if I have the exact same line as
> my original file... but if I overwrite it with the original, it work.

Insufficient information makes it hard to help you. You just vaguely
circumscribe what happened to you, without showing any hard facts, like

1) source code (a small, but still buggy example)
2) compiler error messages (in 'gcc -v' mode, if possible)

Descriptions like 'it doesn't work' or 'it works' tell us nothing
about the nature of your problem. The actual compiler messages usually
do.

This kind of behaviour often is the result of some error elsewhere in
your code, that confuses the compiler enough to make it totally
misinterpret the part of the code that you're working on.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -