diff options
| author | Rafael Garcia-Suarez <rgarciasuarez@gmail.com> | 2009-08-07 13:25:21 +0200 |
|---|---|---|
| committer | Rafael Garcia-Suarez <rgarciasuarez@gmail.com> | 2009-08-07 13:25:21 +0200 |
| commit | 53967bb90ff3867cdf0a6117faed24c717c12c22 (patch) | |
| tree | 19d8a87d750feb5f23e2b64a9c9ed050ed65ddbd /pod/perltodo.pod | |
| parent | ef9da979fc5cddb4c5d039bc1c6205e98c09cc85 (diff) | |
| download | perl-53967bb90ff3867cdf0a6117faed24c717c12c22.tar.gz | |
perltodo: Propagate compilation hints to the debugger
Suggested by Ben Morrow
Diffstat (limited to 'pod/perltodo.pod')
| -rw-r--r-- | pod/perltodo.pod | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/pod/perltodo.pod b/pod/perltodo.pod index ad78744dbc..880fb16fce 100644 --- a/pod/perltodo.pod +++ b/pod/perltodo.pod @@ -898,6 +898,15 @@ L<http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2007-03/msg00481.html> There is no method on tied filehandles to allow them to be called back by formats. +=head2 Propagate compilation hints to the debugger + +Currently a debugger started with -dE on the command-line doesn't see the +features enabled by -E. More generally hints (C<$^H> and C<%^H>) aren't +propagated to the debugger. Probably it would be a good thing to propagate +hints from the innermost non-C<DB::> scope: this would make code eval'ed +in the debugger see the features (and strictures, etc.) currently in +scope. + =head2 Attach/detach debugger from running program The old perltodo notes "With C<gdb>, you can attach the debugger to a running |