Perl would be my prefered choice in this though. The use of such would be great in creating examples in how regexes get processed.
This problem is a bit underspecified. For example, if you give me any sample of, say, 10 URLs
http://www.youtube.com/user/test1 http://www.youtube.com/user/test2 http://www.youtube.com/user/test3
http://www.youtube.com/user/test4 http://www.youtube.com/user/test5:
regex created: http://www.youtube.com/user/(.*)
http://be.apple.itunes.com/blabla/blabla/id/1543285432 http://us.apple.itunes.com/blabla/blabla/id/154328545 http://uk.apple.itunes.com/blabla/blabla/id/5532424342 http://be.apple.itunes.com/blabla/blabla/id/15432
http://be.apple.itunes.com/blabla/id/4324
regex created: http://(\d)+\.apple.itunes.com/blabla/blabla/id/(.*)
In reply to Re^2: Reverse regexp a regexp?
by freakingwildchild
in thread Reverse regexp a regexp?
by freakingwildchild
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |