Re: Inconsistent comma requirements

On 2017-06-26 12:41, hh via use-livecode wrote: No reason to get angry. This thread started from an excellent LC Lesson in the forum ( http://forums.livecode.com/viewtopic.php?f=7=29403 ) There is only one line to know: function logarithmicSearch @pArray pItem pLeft pRight Presumably a lot

Re: Inconsistent comma requirements

> Mark wrote: > >> Monte wrote: > >> I have seen it before in user scripts but never used it myself. > >> It’s one of those things you discover (like when {} could be used > >> interchangeably with []) that you quickly realise you should never > >> rely on so you forget pretty quickly ;-) > > hh

Re: Inconsistent comma requirements

> On 26 Jun 2017, at 4:05 pm, hh via use-livecode > wrote: > >> I have seen it before in user scripts but never used it myself. >> It’s one of those things you discover (like when {} could be used >> interchangeably with []) that you quickly realise you should

Re: Inconsistent comma requirements

On 2017-06-26 08:05, hh via use-livecode wrote: Monte wrote: I have seen it before in user scripts but never used it myself. It’s one of those things you discover (like when {} could be used interchangeably with []) that you quickly realise you should never rely on so you forget pretty quickly

Re: Inconsistent comma requirements

On 2017-06-26 01:42, Monte Goulding via use-livecode wrote: On 25 Jun 2017, at 1:37 am, Richard Gaskin via use-livecode wrote: How many of you have never before known that commas are optional between definition arguments? I have seen it before in user scripts

Re: Inconsistent comma requirements

> Monte wrote: > I have seen it before in user scripts but never used it myself. > It’s one of those things you discover (like when {} could be used > interchangeably with []) that you quickly realise you should never > rely on so you forget pretty quickly ;-) You are member of the LC-team and

Re: Inconsistent comma requirements

> On 25 Jun 2017, at 1:37 am, Richard Gaskin via use-livecode > wrote: > > How many of you have never before known that commas are optional between > definition arguments? I have seen it before in user scripts but never used it myself. It’s one of those things

Re: Inconsistent comma requirements

On 24 June 2017 at 16:37, Richard Gaskin via use-livecode < use-livecode@lists.runrev.com> wrote: > Two questions: > > How many of you have never before known that commas are optional between > definition arguments? > > For those who've known about this, were you confused to discover that this >

Re: Inconsistent comma requirements

On 24 June 2017 at 20:59, hh via use-livecode wrote: > Here's to all who didn't ignore the wonderful LC lessons for years! > > on mouseUp > I > end mouseUp > > on I don't care >answer I'm ("fan of it.") > end I > > function I'm fan >return "Beautiful

Re: Inconsistent comma requirements

Livecode claims that it's programming langauge is English-like (i.e. like a human language); well it just got more like that: human languages are incredibly inconsistent. Richmond. On 6/24/17 10:59 pm, hh via use-livecode wrote: Here's to all who didn't ignore the wonderful LC lessons for

Re: Inconsistent comma requirements

Here's to all who didn't ignore the wonderful LC lessons for years! on mouseUp I end mouseUp on I don't care answer I'm ("fan of it.") end I function I'm fan return "Beautiful LiveCode! I'm " & fan end I'm ___ use-livecode mailing list

Re: Inconsistent comma requirements

Alex Tweedly wrote: > On 24/06/2017 16:37, Richard Gaskin via use-livecode wrote: >> On the other hand, perhaps a rule could be introduced that any >> keywords used in arg strings with no commas when calling a custom >> handler are treated as literal text. > NO, please not. > > Just think of the

Re: Inconsistent comma requirements

On 24/06/2017 16:37, Richard Gaskin via use-livecode wrote: Two questions: How many of you have never before known that commas are optional between definition arguments? For those who've known about this, were you confused to discover that this only works for definitions but not calls?

RE: Inconsistent comma requirements

I have had several of these typos in the past and they never caused problems. In the example below pParam is argument 1. The comma is ignored. command test, pParam answer pParam end test The parser is much better in v8 but could still be tightened up a bit. An example is extraneous closing

Re: Inconsistent comma requirements

On 6/24/2017 11:37 AM, Richard Gaskin via use-livecode wrote: > Two questions: > > How many of you have never before known that commas are optional > between definition arguments? I discovered this in LC6.7.11 only about 2 months ago and was very surprised. I had expected that separating

Re: Inconsistent comma requirements

On June 24, 2017 11:36:32 AM Richard Gaskin via use-livecode wrote: It was just odd to find something so fundamental to the language that I'd never seen before in all my years with LC. And apparently there are at least two of us. Three. -- Jacqueline Landman

Re: Inconsistent comma requirements

Mark Wieder wrote: > On 06/24/2017 08:37 AM, Richard Gaskin via use-livecode wrote: > >>DoSomething with a and b >> >> Two questions: >> >> How many of you have never before known that commas are optional >> between definition arguments? > > > > However, I don't think that particular

Re: Inconsistent comma requirements

On 06/24/2017 08:37 AM, Richard Gaskin via use-livecode wrote: DoSomething with a and b Two questions: How many of you have never before known that commas are optional between definition arguments? However, I don't think that particular syntactic sugar, at least, would work. The