| Re: pointer components and memory leaks |
|
 |
|
 |
|
 |
|
 |
Group: comp.lang.fortran · Group Profile
Author: James Van BuskirkJames Van Buskirk Date: Sep 16, 2008 18:34
"Richard Maine" wrote in message
news:1ind27e.1ueeefs1lcziqcN%%nospam@see.signature...
> Let's not suggest compiler bug every time one finds a problem. While
> compilers have been known to have bugs, those people who first think
> compiler bug every time they see something wrong don't tend to do a very
> good job of debugging... because they too quickly stop looking for their
> own bugs, which are where most bugs are, after all. Calling "compiler
> bug" too quickly is a habit that often has to be "beat out" of new
> users. There sometimes seems to be an inverse correlation in that the
> people who most often suggest they have found compiler bugs are the
> people least likely to have actually done so.
I have found it quite useful to consider a bug that I can't see a
reason for in my code to be a compiler bug. Investigating the
etiology of the compiler bug puts one in a frame of mind where it's
useless to just look at the code; instead one must meticulously test
the consequences of each stage of the program to find where
divergence from the expected occurs. Coincidentally this is also a
constructive frame of mind for locating bugs in code one has just
written. I am certain that I have found hundreds of compiler bugs
this way, too.
--
write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, &
6.0134700243160014d-154/),(/'x'/)); end
| 
