Boost logo

Boost :

From: John (EBo) David (ebo_at_[hidden])
Date: 2001-05-23 03:22:56

Beman Dawes <bdawes_at_[hidden]> writes:
> >"Aleksey Gurtovoy" <alexy_at_[hidden]>:
> >[snip]
> >> So I am all in favor of the new technique!
> >
> >I like it too.
> >
> >> There is one issue with the library that I personally would like to
> >> see resolved at this stage, though: names of the macros. IMO, now they
> >> are too short and too generic for macro names, even with the BOOST_
> >> prefix. I understand that longer names could cause some portability
> >> problems, but still I would prefer to see something less general/more
> >> long in place of BOOST_IF, BOOST_INC or BOOST_DEC. At least the
> >> library name, or some other indication of scope of these macros should
> >> be added, e.g. as I did it in the above example (BOOST_PREPROCESSOR_IF,
> >
> >All of the library, including naming, is obviously tentative at this
> >I would personally prefer a somewhat shorter prefix like CPP, which is
> >name I also had in mind for the library, but I can live with PREPROCESSOR
> >if that is the consensus.
> Pending killer arguments from others, I [slightly] prefer the CPP names,
> although I could certainly live with PREPROCESSOR. But I do agree with
> Alexsey that just plain BOOST_IF, etc, is a bit too generic.

I agree. BOOST_IF... seems way to general, but adding _CPP_ to the name
may throw a few newcomers a bit because of the historical use of CPP to
mean "C++" and not the preprocessor. Coming up with a good naming
convention for this one is likely to be difficult...

  EBo --

Boost list run by bdawes at, gregod at, cpdaniel at, john at