Re: Finder Tell Blocks
Re: Finder Tell Blocks
- Subject: Re: Finder Tell Blocks
- From: John W Baxter <email@hidden>
- Date: Wed, 6 Mar 2002 18:42:15 -0800
At 16:15 +0000 3/6/2002, has wrote:
>
Yeah, that's the trick: comment the stuff that *isn't* obvious, not the
>
stuff that is. Even then, you should still ask yourself:
>
>
1. could the non-obvious code be made easier to comprehend first?
>
>
2. if any obvious stuff only seems that way because your memory of its
>
design and workings is fresh at the time? [Because it won't be six months
>
later...]
>
>
>
Ideally, let the code speak for itself as much as possible. Use comments to
>
*summarise* - i.e. to describe its overall purpose; indicate where and why
>
workarounds and bugfixes have been used; make difficult concepts and
>
principles easy to grasp; suggest how future additions or improvements
>
might be made; etc.
And, now and then (but more rarely than it actually is done) it is
necessary to use some trick to get acceptable performance [your "customer"
may not WANT to run the thing overnight after you show them the 1 minute
version]. (Exaggeration for effect.)
Time here to unleash some fairly extreme comments. Which include the
un-speeded-up code just in case the fast version stops working due to a Mac
OS update.
--John
--
John Baxter email@hidden Port Ludlow, WA, USA
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.