This is a basic question, but I'm hoping someone can help decipher this line of code for me. I can't find a reference anywhere to what the period in this statement does. I assume by the setup that it is some sort of conditional, but would appreciate any further info. Is it Keil specific? Counter[CounterInstance].Output = FALSE
Thanks for the prompt replies, guys. Believe it or not, I was unable to find this syntax in TWO different C books. I suspect it was because I was concentrating on trying to find it in the sections that cover conditionals rather than assignments. I will do some reading up on this operator. Thanks again!
"Believe it or not, I was unable to find this syntax in TWO different C books" The definitive 'C' book must be The C Programming Language by Kernighan & Ritchie (commonly known as "K&R"): http://www.cs.bell-labs.com/cm/cs/cbook/index.html http://www.amazon.co.uk/exec/obidos/ASIN/0131103628/qid=1124807077/sr=1-1/ref=sr_1_10_1/026-5100447-3280432 The dot ("period") operator is actually listed under '.' right at the start of the index of this book - so you'd have no trouble there! "I was concentrating on trying to find it in the sections that cover conditionals" Why? If your 'C' books are so bad that they don't clearly point out the difference between the assignment operator, '=', and equality relational operator, '==', then you should throw them away now! Using '=' when '==' is needed is a classic 'C' programming error! Again, K&R lists '=' and '==' right at the start of the index
In addition to K&R I'd recommend "C - A Reference Manual" by Harbison and Steele. I get the impression that somebody has just plonked a load of code on you and asked you to fix or modify it? If so, good luck, and don't hesitate to post any more questions.
I was unable to find this syntax in TWO different C books That's a symptom of attacking the problem from entirely the wrong direction. You can't seriously expect to understand a completely new language by "finding" individual aspects in a textbook. You have to actually learn the language, and still has to be done by working through a textbook, from cover to cover, not by jumping all over the place with a somewhat involved code example in hand. Once you have got the general picture, you can go back to picking up individual aspects out of the book as you need them, but you absolutely need that general picture first.
Someone did indeed plunk a load of C source code and asked me to do some white box testing of some new revisions. I have much more experience with C++ and Assembly, but minimal C experience. Reading through Dietel and Dietel's "C-How to Program" obviously did not "teach" me the language as it should be taught (with examples, etc), as can be told by how I did not know the answer to this simple question. Thanks again, guys.