Re: [Boost-bugs] [Boost C++ Libraries] #2115: Avoid bad Apple macros

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2115: Avoid bad Apple macros
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2008-07-14 13:42:46

#2115: Avoid bad Apple macros
  Reporter: dave | Owner: bemandawes
      Type: Bugs | Status: new
 Milestone: Boost 1.36.0 | Component: inspection script
   Version: Boost 1.35.0 | Severity: Problem
Resolution: | Keywords:

Comment(by marshall):

 Just F-everyone's-I, here's a list of the macros defined in

 debug_string, check, ncheck, check_string, ncheck_string, check_noerr,
 check_noerr_string, verify, nverify, verify_string, nverify_string,
 verify_noerr, verify_noerr_string, verify_action, require, nrequire,
 require_action, nrequire_action, require_quiet, nrequire_quiet,
 require_action_quiet, nrequire_action_quiet, require_string,
 nrequire_string, require__action_string, nrequire__action_string,
 require_noerr, require_noerr_action, require_noerr_quiet,
 require_noerr_action_quiet, require_noerr_string,

 IMHO, the really nasty ones are: check, verify, require and check_error.

 My suggestion is to #define __ASSERTMACROS__ in the darwin Jamfile, and to
 add a warning to the docs.

Ticket URL: <>
Boost C++ Libraries <>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:49:58 UTC