Re: Since Apple Listens to this List... [Case Statements]
Re: Since Apple Listens to this List... [Case Statements]
- Subject: Re: Since Apple Listens to this List... [Case Statements]
- From: email@hidden (Michael Sullivan)
- Date: Mon, 11 Feb 2002 17:02:39 -0500
- Organization: Society for the Incurably Pompous
Paul Berkowitz writes:
[if else and case blocks demonstrated]
>
[...I don't see what...] would be any different. What's the difference?
Typing. With a case statement you don't have to say 'TheVariable ='
over and over. That's nice when you have a 20+ case switch, which very
occasionally is the only good way to handle a problem.
In general I agree with you though, I don't think a switch/case
statement is any more legible, and is quite a bit *less* legible to
someone who's never seen a declarative programming language before. The
If..else...end if construct generally makes sense to non-programmers.
Given the rarity of needs for really long case switching constructions,
I'd say this is a back burner request at best, nowhere near as important
as hashed arrays, faster event (app and osax) calls, or better library
handling, and obviously just plain making existing features work as
designed in all current systems.
The more I think about it, the more I don't think it's even worth
bothering with. There's no need to recreate C in Applescript. If we
wanted that we'd just use Perl.
Michael
--
Michael Sullivan
Business Card Express of CT Thermographers to the Trade
Cheshire, CT email@hidden
_______________________________________________
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.