Re: Operator vs. Command precedence
Re: Operator vs. Command precedence
- Subject: Re: Operator vs. Command precedence
- From: has <email@hidden>
- Date: Sat, 6 Jun 2009 10:48:41 +0100
Chris Page wrote:
The issue remains that there is no means to indicate that a command is
meant to be treated with some operator precedence
The problem is nothing to do with operator precedence. It's that you
have several syntaxes for expressing a single structure (command), and
the parsing rules for each syntax are different.
There is no satisfactory technical solution to this basic design flaw,
short of redesigning the whole language. All you can do is better
educate users as to the similarities and differences between commands
whose names are identifiers and commands whose names are keywords, and
the gotchas that they need to look out for when dealing with them.
Regards,
has
--
Control AppleScriptable applications from Python, Ruby and ObjC:
http://appscript.sourceforge.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden