2011/7/5 Alexander Kabaev <kab...@gmail.com>: > The slow way would be the right way if you were inclined to really take > it. Once old releases of tools that can be broken by the new macro > use are long and forgotten we can start on relying on said macro, but > not before.
Given that your main concern is backward compatibility, is it an inconvenient to you if 3rd party compilers such as GCC or Clang begin adding this macro? If you're still not comfortable with this macro by the time you want to import one of those, it just takes a minute to remove it. The purpose of this, of course, is to start the clock count (as you've put it: "Once old releases of tools that can be broken by the new macro use are long and forgotten we can start on relying on said macro"). -- Robert Millan _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"