https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250740
--- Comment #4 from Fernando Apesteguía <fern...@freebsd.org> ---
(In reply to Dimitry Andric from comment #3)
Hi Dimitry!
Yes, it does something similar with "and", "or"... and workarounds the problem
by using -fno-name-operators.
Having a look at the code it looks like the author thought that flag would
protect them:
extern "C" {
/* If you use gcc, you may also have to use -fno-operator-names */
#define private cclientPrivate /* private to c-client */
#define and cclientAnd /* C99 doesn't realize that ISO 646 is dead */
#define or cclientOr
#define not cclientNot
#endif
Now, my question is why does it work in different versions of clang, including
the most recent one but seems to fail from time to time across versions?
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
