merge() only evaluating first expression?

Mark Waddingham mark at
Wed Aug 2 16:00:14 EDT 2017

If you evaluate the second expression in that merge in the context (i.e. Same handler) of the call to merge does it throw an error?

If a compile or runtime error occurs in any [[ ... ]] bracketed part of the merge string, then it gets rendered literally and not the value of it (as it can't be evaluated).

Warmest Regards,


Sent from my iPhone

> On 2 Aug 2017, at 21:02, Dr. Hawkins via use-livecode <use-livecode at> wrote:
> Before I file the bug report, I want to check that this is an error (or am
> I missing something
> I have the custom property  blElQry with value
> SELECT kywd FROM [[dhtbl_dat]] WHERE kywd LIKE '[[the leadFdWc of srcRw]]%'
> ESCAPE '\' ORDER BY kywd
> However, the single quote appears to be blocking evaluation of the second
> bracketed term; the first is correctly taken from a variable, but the
> second retains that literal text.
> I don't  believe that LiveCode should be treating a single-quoted range as
> a literal in merge(), should it?
> For that matter, nothing in the dictionary suggests that a double-quoted
> string would be exempt from valuation.
> -- 
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the Use-livecode mailing list