Scripting style: Verbs in function names

[Paul Dupuis]

Of course, just to be contrary, English has lots of grammatical
inconsistencies. So if one of the goals of LiveCode script is to be
"English-like" shouldn't it have a few grammatical inconsistencies too?


On 11/3/2016 7:43 PM, Monte Goulding wrote:
>> On 4 Nov. 2016, at 10:21 am, Phil Davis <revdev at pdslabs.net> wrote:
>>
>> I like Devin's reasoning on this. One of the great benefits we enjoy in using LiveCode is the "English-like" syntax. This is one of LC's hallmark features. As I see it, we should work to preserve it and extend it in our naming of commands and functions.
> I can’t help wondering if there’s a general guideline we can apply here where if there’s a strong case for a verb then refactor as a command and if there isn’t then use a function and leverage the implied verb in the statement. I think there may be an exception with a function that returns a mutated form of the first parameter though (arrayEncode, baseConvert etc), however, they could have easily been commands…
>
> Cheers
>
> Monte
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode