> There's no strong reason to define the macro to the value 1. It's > just what I'm used to. I think I must have seen that it was a common > style and followed it: it looks like about 95% of the /usr/include/*.h > headers on my system here define their header guard macros to the > value 1.
Fine with me. Ethan _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
