Re: [boost] Macros at namespace scope: trailing semicolon?

From: David Abrahams (dave_at_[hidden])
Date: 2005-07-15 11:59:43

Brian Allison <brian_at_[hidden]> writes:

>    David Abrahams wrote:
>
>      I don't know about the priorities of the rest of Boost, but I guess
>      purity is a lower priority for me than some other things.
>
>     FWIW,  this  tells me that I made the better choice to observe Boost,
>    but  not incorporate it yet if at all. At least, until I know what the
>    highest priority are WRT Boost design.

Well, purity is important to me, but I think the following has
something to offer many of us:

  $python -c "import this"
  The Zen of Python, by Tim Peters

  Beautiful is better than ugly.
  Explicit is better than implicit.
  Simple is better than complex.
  Complex is better than complicated.
  Flat is better than nested.
  Sparse is better than dense.
  Readability counts.
  Special cases aren't special enough to break the rules.
  Although practicality beats purity.
  Errors should never pass silently.
  Unless explicitly silenced.
  In the face of ambiguity, refuse the temptation to guess.
  There should be one-- and preferably only one --obvious way to do it.
  Although that way may not be obvious at first unless you're Dutch.
  Now is better than never.
  Although never is often better than *right* now.
  If the implementation is hard to explain, it's a bad idea.
  If the implementation is easy to explain, it may be a good idea.
  Namespaces are one honking great idea -- let's do more of those!

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com