This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Standard scheme for maintainer-only debugging code?
- From: Phil Edwards <phil at jaj dot com>
- To: Nathanael Nerode <neroden at twcny dot rr dot com>
- Cc: geoffk at geoffk dot org, gcc at gcc dot gnu dot org
- Date: Tue, 10 Jun 2003 16:09:45 -0400
- Subject: Re: Standard scheme for maintainer-only debugging code?
- References: <20030610195038.GA19115@doctormoo>
> (How should this be done? In C, declaring constants which can easily be
> made into variables is an odd process, and I'm not quite sure what the
> right magic incantation is. "const static bool debug_XYZ = 0;" ?)
'= false;', but otherwise yes.
> I do worry that there are too many different types of things
> with the debug_ prefix. I want a unique prefix. Perhaps mdbg_ for
> maintainer debug? Or perhaps use the debug_ prefix for this, and stop
> using it for some of the other things it's used for? ???
It would be easier to introduce the new form for new usages, so my vote
would be for mdbg_ for the maintainer debug. (I don't plan on hacking any
core parts of the compiler anytime soon, so weight my vote appropriately.)
As an aside, Nathanael, your mutt seems to be dropping or eliding or
otherwise doing bad things to the References: and In-reply-to: headers.
All of your emails are suffering from "Kenner Syndrome". :-)
Phil
--
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams