Re: Integers and standard
- From: "James Giles" <jamesgiles@xxxxxxxxxxxxxxxx>
- Date: Tue, 29 Jul 2008 00:17:59 GMT
Steven G. Kargl wrote:
In article
<02tjk.138695$102.39915@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>, "James
Giles" <jamesgiles@xxxxxxxxxxxxxxxx> writes:
I certainly think that if the compiler doesn't detect integer
overflow at run-time, there should at least be an option to
ignore the problem at compile-time as well.
-fno-range-check has been availabe for more than 2 years. RTFM.
I see no reason for foul language (unless the F in the above
abbreviationis to be assumed to be other than the usual). I already
stated quite clearly that I don't have gfortran installed. I don't
have the "fine" manual. I don't plan to get it. I was making
a statement about implementations in general. Your's happened
to be the specific one exemplified in the current thread.
--
J. Giles
"I conclude that there are two ways of constructing a software
design: One way is to make it so simple that there are obviously
no deficiencies and the other way is to make it so complicated
that there are no obvious deficiencies." -- C. A. R. Hoare
"Simplicity is prerequisite for reliability" -- E. W. Dijkstra
.
- Follow-Ups:
- Re: Integers and standard
- From: Steven G. Kargl
- Re: Integers and standard
- References:
- Integers and standard
- From: Alfredo Buttari
- Re: Integers and standard
- From: Richard Maine
- Re: Integers and standard
- From: glen herrmannsfeldt
- Re: Integers and standard
- From: Steven G. Kargl
- Re: Integers and standard
- From: James Giles
- Re: Integers and standard
- From: Richard Maine
- Re: Integers and standard
- From: James Giles
- Re: Integers and standard
- From: Steven G. Kargl
- Integers and standard
- Prev by Date: Re: Integers and standard
- Next by Date: Re: Integers and standard
- Previous by thread: Re: Integers and standard
- Next by thread: Re: Integers and standard
- Index(es):