Content-Disposition: inline
X-RT-Original-Encoding: utf-8
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.508 (Entity 5.508)
References: <rt-4.4.1-450-1507900243-1234.0-0-0@isc.org>
 <RT-Ticket-46276@isc.org>
 <rt-4.4.1-95642-1507900432-1472.46276-0-0@isc.org>
X-RT-Interface: Web
Message-ID: <rt-4.4.1-39298-1508215048-1149.46276-0-0@isc.org>
Content-Type: text/plain; charset="utf-8"
In-Reply-To: <rt-4.4.1-95642-1507900432-1472.46276-0-0@isc.org>
RT-Send-CC:
Content-Length: 767

On Fri Oct 13 03:13:52 2017, michal wrote:
> Proposed fix is in rt46276.  It avoids wreaking havoc in generated
> documentation by enabling expansion only for explicitly specified
> macros.  A cursory search through the source tree did not uncover any
> further candidates for special-casing like this, but if it turns out to
> be necessary, more macros may easily be added by following the examples
> from Doxygen documentation [1].
> 
> Please review.
> 
> [1] http://www.doxygen.nl/config.html

LIBRPZ_PF is a similar macro.

Silenced most of the errors from Doxygen.

DNS_MESSAGETEXTFLAG_OMITDOT is still being warned about.   We need to
workout whether to implement or remove from the documentation.  I'll
open a seperate ticket to address this.

Good too commit