Actually this does not use more memory. When the compiler optimizes it
eliminates "unnecessary" variables. I frequently use them to make the code
easier to understand.

As for the other post about the ISR bug in early MikroC compilers. I am not
aware of any current compiler that has the problem. I only posted it to sho=
w
the origin of such concern and that it has been fixed.

Allen

> -----Original Message-----
> From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] On Behalf
Of
> Richard R. Pope
> Sent: Monday, July 21, 2014 9:34 PM
> To: Microcontroller discussion list - Public.
> Subject: Re: [Pic] Making a special timer!
>=20
> James,
>      I can see were this would be easier for someone else to understand
> the code. It would use a little more memory but since it is a local
> variable and this program is so small I don't think that this would be a
> problem. Thanks for the suggestion.
> rich!
>=20
> On 7/21/2014 6:48 PM, James Cameron wrote:
> > On Mon, Jul 21, 2014 at 12:45:09PM -0400, Allen Mulvey wrote:
> >> (A single semicolon ';' can be used in place of the two braces '{}')
> > You mean like this:
> >
> > 	while (count <=3D (time * 10));
> >
> > While true, it is easy to miss on subsequent reading, because it looks
> > so similar to a function call.
> >
> > My C style brain would do this:
> >
> > 	int limit =3D time * 10;
> > 	while (count <=3D limit) continue;
> >
> > And then I'd dislike the <=3D and adjust it some more:
> >
> > 	int limit =3D time * 10 + 1;
> > 	while (count < limit) continue;
> >
>=20
> --
> http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist


--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.