> If anyone wants to provide some rules of thumb for when you use a > function and when you don't, that might be interesting.
In general I use functions when the main point is to process something and return a value, and I use command handlers when I want to "do" something that may or may not return a value. For example, extracting a column of data from a container is a function, while printing something is a command handler. Even though a command handler can return a value, usually this is the exception, not the rule - and most of the time what's returned is an error (if anything). It's a mimic of the language... imagine the "create folder" command being wrapped up in a handler: on CreateFolder pFolderPath create folder pFolderPath put the result into tResult return tResult end CreateFolder Now compare the raw command with the command handler: create folder "MyFolder" if the result is not empty then... --- there's an error CreateFolder "MyFolder" if the result is not empty then... --- there's an error Anyway, that's my 2 cents... Ken Ray Sons of Thunder Software, Inc. Email: k...@sonsothunder.com Web Site: http://www.sonsothunder.com/ _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode