From: Dean M. B. <mik...@gm...> - 2010-01-21 05:43:02
|
On Thu, Jan 21, 2010 at 7:25 AM, Nelson, Erik - 2 <eri...@ba...> wrote: > Dean Michael Berris wrote: >> I think it's because vendors aren't quick to support them natively in >> the compiler. GCC takes this in stride just fine as does other >> vendors (Intel's compiler is another one I know that works pretty >> well). I would quote the appropriate parts of the C++ standard if I >> had a copy (which I promise I should buy someday soon) but anyway >> it's something really annoying to me for non-conformant compilers >> like MSVC. >> >> I also like them better but unfortunately to support more compilers >> we're going to have to stick with !, ||, && et al. > > I'd say just put #include <ciso646> up high and continue to use them. > They are standard C++, and they're much more descriptive than the !&&#|| > stuff. Don't cave in to the noncompliant compiler vendors! > Yeah, I suppose that would work. ;) -- Dean Michael Berris cplusplus-soup.com | twitter.com/deanberris linkedin.com/in/mikhailberis | facebook.com/dean.berris | deanberris.com |