 variables and statements
	do not modify the behavior of the routine: executed outside a debugging session, it
	should act exactly the same way as a "normal" routine with no debug info.
</p>
<p>
	This also makes for a routine's code bloat and possible slow down to to the fact it is
	interpreted by MySQL (therefore more code to interpret).
</p>
<p>
	Once the debugging session is complete, one wishes to remove the injected debug code
	from the routine. <i>rdebug_compile_routine()</i> will strip down the debug