Yes, I did miss that. I think we're getting a bit off topic (Falcon), but I'm curious and looked into this a bit further.
It looks like the assignment resolves to 'undefined' if the second part is null, NOT to boolean false. But the result seems to be the same, so I am stopping now. It's all good: this confirms Falcon throws the same warning as the classic compiler when encountering an assignment in an if-statement. EdB On Wed, Sep 11, 2013 at 4:12 PM, John Cunliffe <mahn...@gmail.com> wrote: > columnIndicator != null > > Did my previous mail not make it? > > On Wed, Sep 11, 2013 at 3:47 PM, Erik de Bruin <e...@ixsoftware.nl> wrote: > >> columnIndicator -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
