Re: Avoiding == and = mixup in if statements
Re: Avoiding == and = mixup in if statements
- Subject: Re: Avoiding == and = mixup in if statements
- From: David Blanton <email@hidden>
- Date: Tue, 25 May 2004 10:10:54 -0600
On 5/25/04 7:53 AM, "Jim Rankin" <email@hidden> wrote:
>
On May 21, 2004, at 7:33 PM, David Blanton wrote:
>
>
> I think that anyone who make the = when it should be == error more
>
> than once
>
> should reconsider their position. McDonalds has pictographs on their
>
> keyboards to prevent this kind of error. :-|
>
>
Wow! I never realized those cash register operators were typing C
>
expressions when they took my order! I have a new found respect for
>
the quality of McDonald's employee training program.
>
>
Maybe if we all started using McDonald's cash registers for keyboards,
>
we could avoid the =, == mixup, too.
>
>
-jimbo
>
Years ago I met a software engineer who wrote quality code from the get go.
No dumb errors e.g. = for ==. I asked him how he managed this feat and his
answer has stayed with me and is the motivation for my comments on this
subject.
"When I started programming I kept, and still keep, an engineering notebook
by my side. I record every error with the objective of never committing
that error again."
I have often wished I had kept that same notebook for when I commit the same
error twice I do not feel like a professional I just feel stupid.
db
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.