Macro names are prone to collisions

[andres-erbsen]

Using single words as macro names can lead to obscure compilation errors. For example, the ev namespace in libev C++ library has constants named READ and WRITE. Defining macros with the same names makes these constants inaccessible.
libev has a C library too and there the ev::READ constant is called EV_READ. A similar emulation of namespaces is probably needed for libsocket.

Some macro names from libsocket code: READ, WRITE, TCP, UDP, STREAM, VERBOSE, BACKLOG, BOTH, NUMERIC.

[dermesser]

What do you think of renaming them to LIBSOCKET_READ, LIBSOCKET_TCP etc.?

[dermesser]

master...new-macro-names

I hope I replaced everything.