From: Nicholas Clark <nick@ccl4.org>
Date: Tue, 2 Jun 2009 12:53:19 +0000 (+0100)
Subject: Disentangling -g and -DDEBUGGING is a TODO.
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=ab45a0fa26b7a5ed9c49aa02ce422deee5e12a05;p=p5sagit%2Fp5-mst-13.2.git

Disentangling -g and -DDEBUGGING is a TODO.
---

diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index 73495cb..c84b51e 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -377,6 +377,15 @@ see if there would be a way to use our existing metaconfig units to configure a
 Windows Perl or whether we go in a separate direction and make it so.  Of 
 course, we all know what step 3 is.
 
+=head2 decouple -g and -DDEBUGGING
+
+Currently F<Configure> automatically adds C<-DDEBUGGING> to the C compiler
+flags if it spots C<-g> in the optimiser flags. The pre-processor directive
+C<DEBUGGING> enables F<perl>'s command line <-D> options, but in the process
+makes F<perl> slower. It would be good to disentangle this logic, so that
+C-level debugging with C<-g> and Perl level debugging with C<-D> can easily
+be enabled independently.
+
 =head1 Tasks that need a little C knowledge
 
 These tasks would need a little C knowledge, but don't need any specific