LMPX.COM |
Home | Linux | Mysql | PHP | XML | ||
|
|
|||
From: Richard Foley Date: Thu Jun 7 03:03:13 2007 Subject: Re: Unreliable breakpoint path specification
On Wednesday 06 June 2007 19:59, Jan Ploski wrote: > > > > What would be the best way to suggest an API extension to perl5db.pl > > > maintainer(s)? > > > > > The best thing is probably to send a patch to P5P and let them take a look > > at it. > > Ok, in that case I'd have to generalize my on load hook first to make > it independent from EPIC. > I'm not familiar with EPIC, but there are a number of cases where the debugger has been quite literally hacked to work with various OS's, terminals, certain libraries and so on. In these cases a sensible solution has often been to seperate the specific stuff via an environment variable. This only applies, of course, if it has no value for other users. Something like PERL5DB_EPIC=1 might do the trick, although you might very well have a more suitable suggestion. Then send a patch to p5p for Rafael to consider applying it to bleed. -- Richard Foley Ciao - shorter than aufwiedersehen http://www.rfi.net/
| Navigate in group perl.debugger at sever nntp.perl.org | |
| Previous | Next |
| © No Copyright You are free to use Anything |
Site Maintained by PHP Developer
Powered By PHP Consultants |