Re: ≠ or not equal

On 03/17/2016 07:02 AM, Richard Gaskin wrote: > "!=" is a good solution (as it is one out of the ASCCI 7-bit range). Agreed. I was very impressed Mark Wieder implemented that as quickly as he did - thanks Mark! @mwieder: Thanks for your contribution. Unfortunately, though, we don't feel

Re: ≠ or not equal

On 17/03/2016 16:27, Mark Wieder wrote: On 03/17/2016 07:02 AM, Richard Gaskin wrote: > "!=" is a good solution (as it is one out of the ASCCI 7-bit range). Agreed. I was very impressed Mark Wieder implemented that as quickly as he did - thanks Mark! @mwieder: Thanks for your contributio

Re: ≠ or not equal

On Mar 17, 2016, at 12:27 PM, Mark Wieder wrote: > On 03/17/2016 07:02 AM, Richard Gaskin wrote: > >> > "!=" is a good solution (as it is one out of the ASCCI 7-bit range). >> >> Agreed. I was very impressed Mark Wieder implemented that as quickly as >> he did - thanks Mark! >> > > > @mwiede

Re: ≠ or not equal

I think the answer is simple and has already been suggested in this thread. Rely on “is not” and remove ≠ for completeness and ensure that when a script includes ≠ on a Mac it will not compile. Although I have filed a bug, I don’t believe LC have decided what to do yet? It’s not hard to travers

Re: Re: ≠ or not equal

I think it is important to remember the following quote: "There are two hard things in computer science: cache invalidation, naming things, and off-by-one errors." At the end of the day syntax largely comes down to naming things - it is really not an easy task at all. On 2016-03-17 17:51, R

Re: ≠ or not equal

> On 17 Mar 2016, at 10:43 AM, Mark Wieder wrote: > > On 03/16/2016 07:18 AM, Richard Gaskin wrote: > >> If we were to look for not-equal-to operators that affect large numbers >> of people, it might be worth considering supporting "!=", since a >> majority of other languages support so for tod

Re: ≠ or not equal

I didn’t say it mattered only that the two systems did not work the same. So, when you get a stack that has been created on a mac that includes ≠ will it matter then? Terry > On 16 Mar 2016, at 10:00, RM wrote: > > So it really doesn't matter that '≠' doesn't work in Linux. _

Re: ≠ or not equal

I think for my part that either translation or on the fly linting in the script editor covers the occasional brain fart situation I was talking about. Or even just compilation errors that deal specifically with users entering the wrong operators. Sent from my iPhone > On 18 Mar 2016, at 5:11 A

Re: ≠ or not equal

I’ll let more experienced LiveCode developers & LiveCode themselves decide that one. It doesn’t matter to me one way or another. If it’s decided to omit it from Mac then it will need to be flagged in a compile. All the best Terry > On 16 Mar 2016, at 12:09, RM wrote: > > OK, Terry: Good po

Re: ≠ or not equal

Bug Filed: Bug 17143 All the best Terry ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://

Re: ≠ or not equal

On 03/17/2016 09:34 AM, Peter TB Brett wrote: In the interests of completeness, maybe it would be helpful to quote the comment [1] fully: Peter - sorry, wasn't trying to censor it, just trying to cut down on list traffic. I see I wasn't successful. -- Mark Wieder ahsoftw...@gmail.com ___

Re: ≠ or not equal

the extended Macintosh codeTable (here: char 173) and the differences to Latin-1 (or HTML entities, where ­ is ­ the optional hyphen) etc. "!=" is a good solution (as it is one out of the ASCCI 7-bit range). -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/o

Re: ≠ or not equal

Mark Waddingham wrote: > Richard Gaskin wrote: >> Esp. given that "<>" is supported but almost unique to our language.. > > "<>" is certainly not unique to our language. Indeed see here: > > https://en.wikipedia.org/wiki/Relational_operator > > The use of <> is predominant in Pascal-like and

Re: ≠ or not equal

't a=b end mouseUp on isn't that if that then answer "Yes, it is!" else answer "No, sorry no, it isn't." end isn't -- or, less wordy: on isn't that answer that end isn't I love LiveCode. -- View this message in context: http://runtime-re

Re: ≠ or not equal

On 03/16/2016 07:18 AM, Richard Gaskin wrote: If we were to look for not-equal-to operators that affect large numbers of people, it might be worth considering supporting "!=", since a majority of other languages support so for today's audience (and more importantly tomorrow's) that habit impacts

Re: Re: ≠ or not equal

-hh wrote: >> R.G. wrote >> If we were to look for not-equal-to operators that affect large >> numbers of people, it might be worth considering supporting "!=", >> since a majority of other languages support so for today's audience >> (and more importantly tomorrow's) that habit impacts orders of

Re: Re: Re: ≠ or not equal

> R.G. wrote > If we were to look for not-equal-to operators that affect large numbers > of people, it might be worth considering supporting "!=", since a > majority of other languages support so for today's audience (and more > importantly tomorrow's) that habit impacts orders of magnitude more

Re: ≠ or not equal

uot;≠" works in v.6.8. I hate "<>". Craig Newman -Original Message- From: Terence Heaford To: How to use LiveCode Sent: Wed, Mar 16, 2016 5:10 am Subject: ≠ or not equal I have been advised that ≠ (not equal) does not compile in Linux.It does seem to work in OSX

Re: Re: ≠ or not equal

RM wrote: > So what? Big deal! Hardly worth the fuss! > > I just tried this: > > on mouseUp > put fld "fff" into FFF > if FFF is not 1 then >put "NOPE" > else >put "YEP" >end if > end mouseUp > > So it really doesn't matter that '≠' doesn't work in Linux. Or:

Re: ≠ or not equal

OK, Terry: Good point! The best thing to do, probably, is to remove the '≠' capability completely, cross-platform. Richmond. On 16.03.2016 14:03, Terence Heaford wrote: I didn’t say it mattered only that the two systems did not work the same. So, when you get a stack that has been created o

Re: Re: ≠ or not equal

Mark Wieder wrote: On 03/17/2016 07:02 AM, Richard Gaskin wrote: >>> "!=" is a good solution (as it is one out of the ASCCI 7-bit range). >> >> Agreed. I was very impressed Mark Wieder implemented that as quickly >> as he did - thanks Mark! > > > > @mwieder: Thanks for your contribution. Unfort

Re: ≠ or not equal

So what? Big deal! Hardly worth the fuss! I just tried this: on mouseUp put fld "fff" into FFF if FFF is not 1 then put "NOPE" else put "YEP" end if end mouseUp So it really doesn't matter that '≠' doesn't work in Linux. Richmond. On 16.03.2016 11:36, Peter TB Brett

Re: ≠ or not equal

On 16.03.2016 11:36, Peter TB Brett wrote: On 16/03/2016 09:09, Terence Heaford wrote: I have been advised that ≠ (not equal) does not compile in Linux. It does seem to work in OSX. If ≠ is not a keyword then why does it work in OSX? Hi Terence, Ali and I had a brief look into this, and

Re: ‚ or not equal

Yeah I lost about half a day to that one a few weeks back trying to figure out why my Android app was failing while the iOS one was fine. Terry... On 16/03/2016 8:09 pm, "use-livecode on behalf of Terence Heaford" wrote: > >I have been advised that ‚ (not equal) does not compile in Linux. > >It

Re: ≠ or not equal

> On 16 Mar 2016, at 8:36 PM, Peter TB Brett wrote: > > * it works on OS X > * it doesn't work on Linux > * there's no immediately obvious reason for this Interesting, I presume this is a hangover from natively encoded scripts and HyperCard support. Now that scripts are unicode has anyone chec

Re: ≠ or not equal

On 2016-03-16 10:36, Peter TB Brett wrote: On 16/03/2016 09:09, Terence Heaford wrote: I have been advised that ≠ (not equal) does not compile in Linux. It does seem to work in OSX. If ≠ is not a keyword then why does it work in OSX? Hi Terence, Ali and I had a brief look into this, and we

Re: ≠ or not equal

On 16/03/2016 09:09, Terence Heaford wrote: I have been advised that ≠ (not equal) does not compile in Linux. It does seem to work in OSX. If ≠ is not a keyword then why does it work in OSX? Hi Terence, Ali and I had a brief look into this, and we can confirm that: * it works on OS X * it

≠ or not equal

I have been advised that ≠ (not equal) does not compile in Linux. It does seem to work in OSX. If ≠ is not a keyword then why does it work in OSX? Thanks Terry ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to su