[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
*hit self on head*
I knew when I wrote if (x == TRUE) that that was one of the problem
cases, just forgot why. Anyway, you got my point about writing
"proper" conditionals. I tend to always write "if (x)" anyway, I
dislike even things like "if (set_gfx_mode() < 0)". Unfortunately with
multiple return values that can't always be helped.
> Oh, and just to say, I'm perfectly happy to see TRUE and FALSE removed
> entirely.
Me too. I don't use TRUE and FALSE because I never know when they will
or will not be defined, and I dislike defining my own in a
preprocessor macro, for reasons you mentioned before. I do use the C++
true and false constants, together with the bool type.
Sounds like removing them completely would be the most consistent,
except it may cause unwanted breakage of backward compatibility. Are
TRUE and FALSE used in the allegro internals at all?
Hein
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<
Unix is user friendly. It's just very particular about who
it's friends are.
Hein Zelle hein@xxxxxxxxxx
http://www.icce.rug.nl/~hein
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<