Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
See also this thread.

The short answer is that you can do this by converting regular expressions to NFAs/DFAs (for more details, see my reply in the thread I referenced). However, this cannot be done in a super-efficient way. In fact, the problem of deciding equivalence of two regular expressions is PSPACE-complete (which is bad ;)). Even in your special case of deciding whether a regular expression accepts all strings, the problem remains PSPACE-complete (google for regular expression universality).

Being PSPACE-complete does not mean it's impossible. It's quite possible, but will quickly become very impractical for large regular expressions..

As for how to do the conversion to NFA/DFA, I can tell you that another monk and I are working on a formal language & automata toolkit that will make this easy, but it won't be ready for a while...

Update: as for your idea above to "simplify" a regex, that is essentially the same thing and will not gain you anything. Testing regex equivalency reduces to the problem of finding the "simplest" equivalent regex (no matter how you define "simplest"), so regex simplification is still a PSPACE-hard problem (-hard instead of -complete because we're now talking about a search procedure, not a decision procedure).

blokhead


In reply to Re: Testing regex equivalence by blokhead
in thread Testing regex equivalence by loris

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others rifling through the Monastery: (2)
As of 2024-04-20 04:19 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found