Re: Automatically transform or expand do loop in a subroutine
- From: "James Giles" <jamesgiles@xxxxxxxxxxxxxxxx>
- Date: Thu, 31 Jan 2008 20:09:23 GMT
Tim Prince wrote:
....
Perhaps i and l aren't good choices for newsgroup posts. It was
difficult enough to remove obvious mistakes from my response.
That's one of the reasons I don't have a rigid case convention in
my coding style. In any situation where it might be misread,
I use capital L in identifiers and lower-case i, to distinguish
them from one (1). I also use z, s, and o to distinguish them
from 2, 5, and 0 respectively.
--
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
.
- References:
- Automatically transform or expand do loop in a subroutine
- From: yaqi
- Re: Automatically transform or expand do loop in a subroutine
- From: Richard Maine
- Re: Automatically transform or expand do loop in a subroutine
- From: highegg
- Re: Automatically transform or expand do loop in a subroutine
- From: Richard Maine
- Re: Automatically transform or expand do loop in a subroutine
- From: Tim Prince
- Automatically transform or expand do loop in a subroutine
- Prev by Date: Re: Automatically transform or expand do loop in a subroutine
- Next by Date: Re: Automatically transform or expand do loop in a subroutine
- Previous by thread: Re: Automatically transform or expand do loop in a subroutine
- Next by thread: Re: Automatically transform or expand do loop in a subroutine
- Index(es):
Relevant Pages
|