True.
I was thinking only "true"/
-Original Message-
From: Dr. Hawkins
To: How to use LiveCode
Sent: Tue, Jun 26, 2012 12:54 am
Subject: Re: is evaluation order defined, and evaluation of conditionals"and"
to "or
On Monday, June 25, 2012, wrote:
>
&g
On Tue, Jun 26, 2012 at 8:48 AM, Bob Sneidar wrote:
> Foxpro was the same way. I think all modern languages work like that.
Not all--modern Fortran explicitly does not guarantee such things--but
that's part of a design to allow massive optimization for parallelism
--
The Hawkins Law Firm
Richa
Foxpro was the same way. I think all modern languages work like that. It allows
the developer to prioritize statements in the order of least to greatest cost.
For most things no one would notice the difference, but for some operations it
may make a big difference.
Bob
On Jun 25, 2012, at 9:3
On Monday, June 25, 2012, Jerry Jensen wrote:
> I had that drilled into my alleged mind in the late '60s in a Boolean
> Algebra class I talked my way into. In those days minimization was
> important because each gate cost a few bucks!
Yes, and a 16 pin dip had four 2 input gates. So if you had
I had that drilled into my alleged mind in the late '60s in a Boolean Algebra
class I talked my way into. In those days minimization was important because
each gate cost a few bucks!
It was sort of a geeky joke then that you could actually build any logic net
using nothing but NAND gates.
.Jer
On Monday, June 25, 2012, wrote:
>
>
> "or" is a simpler case, as there is never a need to evaluate after
> a first round "true". Again, at least externally.
>
No, they're not.
OR is "when both inputs are false, output is false (else its true)"
AND is "when both inputs are true, output is true (e
Jerry wrote":
similarly if "or" is used instead of "and",
> if the first part evaluates to "true", the second is NOT called.
"or" is a simpler case, as there is never a need to evaluate after
a first round "true". Again, at least externally.
I changed the "and" to "or" in Jerry's example, and
