Functions of '?', ':', and '&' in the C programming language

[DanDon]

What are the functions of the ? and the : in the following C statement?


TX_OUTPUT_PIN = Tx_Buffer & 0x01 ? SERIAL_1 : SERIAL_0;


Another question, can someone please clearly explain the purpose (And usage) of the bitwise AND operator?

Thank you very much,

[Greg Ross]

The ?: is called the ternary operator because it takes three operands. It's shorthand for "If the first operand is true, return the value of the second operand, otherwise, return the value of the third."

The & is a bitwise AND. The value returned has a 1 in each bit that is set in both operands. All other bits are zero.

In this example, the low order bit of Tx_Buffer is tested, and if it is set, TX_OUTPUT_PIN is assigned the value SERIAL_1, otherwise SERIAL_0.

BTW, I generally steer away from using the ternary operator. The following is much clearer:
if (Tx_Buffer & 0x01 == 1)
TX_OUTPUT_PIN = SERIAL_1;
else
TX_OUTPUT_PIN = SERIAL_0;

[DanDon]

Please pardon my ignorance, but what does the 0x01 do when the bitwise AND is used on it and Tx_Buffer?

Thank you so much for your reply,

[Matt Leese]

Please pardon my ignorance, but what does the 0x01 do when the bitwise AND is used on it and Tx_Buffer?

Thank you so much for your reply,
The bitwise operators work at the bit level. It will do a bitwise AND on each and every bit. So, if the low-bit of Tx_Buffer is 1, the output will be 1. Otherwise it will be 0.

Assuming Tx_Buffer = 0x41, the comparison would look like:


0000 0001
& 0100 0001
-----------------
0000 0001


Matt

[DanDon]

The bitwise operators work at the bit level. It will do a bitwise AND on each and every bit. So, if the low-bit of Tx_Buffer is 1, the output will be 1. Otherwise it will be 0.

Assuming Tx_Buffer = 0x41, the comparison would look like:


0000 0001
& 0100 0001
-----------------
0000 0001


Matt

Thanks for the reply Matt, that really clarified my understanding of the bitwise AND operator.

Thanks again,

[Chris Hibner]

The ?: is called the ternary operator because it takes three operands. It's shorthand for "If the first operand is true, return the value of the second operand, otherwise, return the value of the third."

The & is a bitwise AND. The value returned has a 1 in each bit that is set in both operands. All other bits are zero.

In this example, the low order bit of Tx_Buffer is tested, and if it is set, TX_OUTPUT_PIN is assigned the value SERIAL_1, otherwise SERIAL_0.

BTW, I generally steer away from using the ternary operator. The following is much clearer:
if (Tx_Buffer & 0x01 == 1)
TX_OUTPUT_PIN = SERIAL_1;
else
TX_OUTPUT_PIN = SERIAL_0;

As much as I hate "yeah, me too" posts, I'm going to do it here...

I strongly recommend staying away from the ternary operator. I also strongly recommend staying away from any other practice that makes your code less clear than it has to be. Good clear code trumps keystroke efficiency in all cases - don't forget that.

During the FRC Championship conference, myself and a colleagure presented an "Advanced C Programming" lecture. The main focus of the lecture was to show how C programming is done in the real-time embedded industry. We tried to impress as much as possible on "good coding practices". While it wasn't in the presentation, we made mention of staying away from the ternary operator (as well as recursion, compound statements, leaving out the {} from code blocks, etc.).

The following web page: http://www.andromeda.com/people/ddyer/topten.html is a great list of C "gotcha's". 90% of them are avoided by using the good practices we recommend. As a side note, the good coding practices that we recommend are basically part of a coding standard that is typical in industry.

Okay, sorry for getting this thread off topic...

[Greg Ross]

...(as well as recursion, compound statements, leaving out the {} from code blocks, etc.).Yeah. I know I violated this one. I should have writtenif (Tx_Buffer & 0x01 == 1) {
TX_OUTPUT_PIN = SERIAL_1;
} else {
TX_OUTPUT_PIN = SERIAL_0;
}(Or is itif (Tx_Buffer & 0x01 == 1)
{
TX_OUTPUT_PIN = SERIAL_1;
}
else
{
TX_OUTPUT_PIN = SERIAL_0;
}?) There are so many opinions about where to place the braces, I decided to leave them out... just this once! I swear! :o

[Ben Margolis]

During the FRC Championship conference, myself and a colleagure presented an "Advanced C Programming" lecture.

I just want to say that I like the website and I'm really sorry I missed the lecture. Is there anywhere where an overview of it can be found? I'm all for spreading the C knowledge.

[Chris Hibner]

I just want to say that I like the website and I'm really sorry I missed the lecture. Is there anywhere where an overview of it can be found? I'm all for spreading the C knowledge.

The conference material can be found here:

http://www.usfirst.org/robotics/2005/Workshops/wrkpresentations.htm