in the extreme development model, the task of removing the debug statements rarely gets prioritized to the point of happening. Popularizing constant-based debug statements as a best practice is certainly an approach; maybe if we get some power to impose standards by refusal we can insist that all debug blocks must be constant-based. But what is 4M in 2006? A lot less than it used to be. When I grew up we had to build our own abaci out of dry spaghetti and dirt clods.
With the new and improved source filter on include directory support one might be able to create a debug block eliminator source filter that essentially does s/\$Debug\w*/0/gi at use time, but there is the possibililty that someone is not following that convention. On 8/16/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
What is now driving me crazy is this: a lot of the frameworks / libraries I use have $Debug statements, so you can profile already running code...
-- David L Nicol Luddite! (mob of angry villagers with ray guns)
