Skip Menu |

This queue is for tickets about the Regexp-Debugger CPAN distribution.

Report information
The Basics
Id: 123134
Status: resolved
Priority: 0/
Queue: Regexp-Debugger

People
Owner: Nobody in particular
Requestors: TWrona [...] iso-ne.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Regexp::Debugger doesn't seem to work within a Perl Module
Date: Tue, 26 Sep 2017 20:11:54 +0000
To: "bug-regexp-debugger [...] rt.cpan.org" <bug-regexp-debugger [...] rt.cpan.org>
From: "Wrona, Timothy" <TWrona [...] iso-ne.com>
The Regexp::Debugger module only seems to work in .pl scripts and doesn't seem to work within a .pm module. See the following stack overflow post for more details: https://stackoverflow.com/questions/46414292/regexpdebugger-perl-module-doesnt-seem-to-work-within-another-perl-module
Subject: Re: [rt.cpan.org #123134] Regexp::Debugger doesn't seem to work within a Perl Module
Date: Wed, 27 Sep 2017 06:55:21 +1000
To: bug-Regexp-Debugger [...] rt.cpan.org
From: Damian Conway <damian [...] conway.org>
Hi Timothy. Thanks for the bug report. I have tweaked the lexical hints look-up to remove the error you encountered. Otherwise, your test code ran perfectly under my latest release (which I just uploaded to CPAN). Please wait for that upload to propagate, then download this latest version and see if it solves your issue. Damian
Subject: RE: [EXT] Re: [rt.cpan.org #123134] Regexp::Debugger doesn't seem to work within a Perl Module
Date: Wed, 27 Sep 2017 13:34:48 +0000
To: "bug-Regexp-Debugger [...] rt.cpan.org" <bug-Regexp-Debugger [...] rt.cpan.org>
From: "Wrona, Timothy" <TWrona [...] iso-ne.com>
Thanks Damian, That fixed the problem! Unfortunately there still seems to be one more issue. I am trying to use this module to debug a rather large regular expression with multiple nested defined groups and I am attempting to parse a file that is more than 36000 lines long. The regular expression match itself will complete in about 200ms, but when I attempt to use the debugger it takes about 2-3 seconds to go between each step. If I attempt to "step over" a defined block it takes so long that it effectively hangs the program entirely. I know this is a rather extreme case and the solution may be to just make smaller files to parse for debugging purposes, but I figured I would let you know so you could look into it and see if there are any easy changes that could be made to improve performance. I would share the regex I am using and the file that I am trying to parse, but I think the code I am parsing is a proprietary language and I am probably not supposed to share it outside of the company. Thanks, Tim Show quoted text
-----Original Message----- From: damian@conway.org via RT [mailto:bug-Regexp-Debugger@rt.cpan.org] Sent: Tuesday, September 26, 2017 4:57 PM To: Wrona, Timothy Subject: [EXT] Re: [rt.cpan.org #123134] Regexp::Debugger doesn't seem to work within a Perl Module *** EXTERNAL email. Please be cautious and evaluate before you click on links, open attachments, or provide credentials. *** <URL: https://rt.cpan.org/Ticket/Display.html?id=123134 > Hi Timothy. Thanks for the bug report. I have tweaked the lexical hints look-up to remove the error you encountered. Otherwise, your test code ran perfectly under my latest release (which I just uploaded to CPAN). Please wait for that upload to propagate, then download this latest version and see if it solves your issue. Damian
Subject: Re: [EXT] Re: [rt.cpan.org #123134] Regexp::Debugger doesn't seem to work within a Perl Module
Date: Thu, 28 Sep 2017 08:22:46 +1000
To: bug-Regexp-Debugger [...] rt.cpan.org
From: Damian Conway <damian [...] conway.org>
Hi Tim, I'm glad the update fixed the bug. As regards performance, if there were any easy changes I could make to improve the performance of the module, I would most certainly have made them. I too need to debug large regexes, and I'vealready done what I can to speed that up. Of course, if you have a patch that would improve performance further, I'd be delighted to consider it. Otherwise, all I can suggest is smaller test data. Damian