Thread: Newbie needs help plz

He didn't, but you just did; MSVC.

So why asking something if you know the answer? wait... don't answer that. I know the answer

Originally Posted by twomers

>> #define AND &&
>> #define OR ||

Bad bad bad. That's like saying:

#define begin {
#define end }
blah blah

then you can do C or C++ in pascal. There's no need to do the above, && and || etc are fine IMO.

Hardly. Not only are the quoted macros not "bad bad bad", they have a legitimate purpose. For example, what if you have a keyboard that doesn't support the requisite characters? C supports trigraphs for that reason, and C++ supports trigrahs and digrahs. In fact, C blesses the idea with the iso646.h header where the macros aren't much different, and C++ reserves actual keywords such as "and", "or", and "not", for the same purpose.

How many keyboards do you know that don't have a # on them!!?

The #define is always good for a little obfuscation

>But to be honest, how many keyboards do you know which don't have &'s or |'s or whatever?
None, but my experience with other keyboard layouts is very minimal.

>I was always told that that kind of defining is 'bad bad bad' ...
For the most part it is. If there weren't a standard solution, I would be hesitant to even talk about it unless asked a pointed question.

>>AND is legal if you #include <iso646.h>
That header is the one I pointed to.

>>Also, I don't see any '?' for a question
This is my post:

If you see my and Wraithan answer is the same, its because we send it at the same time. Unfortunately I only solved the problem that OP pointed I didn't mention whole the code.
Now it seems that OP problem is solved somehow, but I have question: How OP code can ever be compiled with that AND? <<<<THIS IS THE QUESTION MARK
I remember a header with these defines:

Code:

#define AND &&
#define OR ||

...But this header is not included in OPs code.

Review the thread.