FALSE AND TRUE in C language

Hi guys !
the teacher once I learned the C programming language just said like this : if (false) then we aren't entering the block of "if", but once if(true) then it enters the block statement of "if", my question is why really the PC works like this, I mean why actually "if (false) " then the PC wouldn't enter the if statement .. ? I can just say it's like that moded .. but how it's translated "false" to PC and why it leads him to not entering the if statement? .. for instance why at "if(true)" the pc actually enters the if statement other than not choosing the choice "not entering it"? why "if (true)" doesn't mean for instance "not entering the block statement" ?!

false => 0
true => everything else.

Simple answer: LOGIC.

Quote:

---

Originally Posted by RyanC

why "if (true)" doesn't mean for instance "not entering the block statement" ?!

---

Because the people who came up with that language feature weren't as prone to overthinking and confusing themselves as you are.

RyanC, the mystery you're probing is found by knowing assembler, and how the CPU operates. It is rather primitive, which means writing to the CPU in it's own language is rather detailed, tedious and uncomfortable.

C was created, originally, for the purpose of writing an operating system. That operating system had already been written in assembler, for a particular CPU. C was intended to function in place of that assembler, without any direct reference to any particular CPU (which means for any CPU).

As a result, the language does have certain technical association with assembler, and I've found knowing assembler to be enlightening on questions just like you've posed.

However, I come from a different era, the '70's and 80's. Although I've kept my skills very current, my own early study naturally involved more primitive hardware and primitive languages. It may not be as practical today.

If you were a serious student and not merely curious, I might recommend a tour of assembler.

Otherwise, however, I'm convinced such things will remain a mystery.

@Niccolo, RyanC is our resident troll - who was banned for a while.
He's been here 4.5 years, but hasn't learnt anything.
Next thing he'll be worrying about is how electrons "know" whether to go through a transistor gate or not.

Quote:

---

Originally Posted by Salem

@Niccolo, RyanC is our resident troll - who was banned for a while.
He's been here 4.5 years, but hasn't learnt anything.
Next thing he'll be worrying about is how electrons "know" whether to go through a transistor gate or not.

---

just to laugh :)
the electrons wouldn't go to the transistor gate if there was
an equal potential between Drain and source xD :)

I don't know if I'm stupid that much or you guys trying to make me stupid ..
if a programmer doesn't know actually why if (true) then the PC enters the if statement and why for isntance if (true) not actually choosing the choice "not entering the statement" .. then wouldn't be a good programmer ..

where's the problem? I want to know why is that true .. I can't everything say "yes it's like this ..that's not learning ... we are not in learning medicine this as this .. "

My question is really explicitly asked .. why actually "true" correspond to satisfying what's found inside if statement .. why actually not the opposite .. not doing the if statement by putting "true" inside if?

Closed another RAFB thread.

Quote:

---

Originally Posted by RyanC

why actually not the opposite .. not doing the if statement by putting "true" inside if?

---

Tell you what: if you pay me $100, then I will transfer ownership of my house to you.

Of course, when you pay me $100, I will then tell you: it is true that you've paid me $100, therefore I will not transfer ownership of my house to you. Thanks for the $100, RyanC!