I don't know, but this is what the author of the 'learn regex the hard way' book has to say:-
/The key to using regular expressions correctly is to know where their usefulness ends and when you need to bust out a lexer. You also need to know where a lexer falls down and when a parser is the right tool. When you use regular expressions to simplify creating lexers that feed into simple parsers you then have a set of tools for cleaning and accurately parsing text without going insane. In this book I'm going to subversively teach you parsing, but I'm going to be very practical and straight forward about it. No NFA to DFA conversion. No crazy explanations of push down finite state automata. Just practical code that gets you introduced to the basics of parsing, understanding the core theory, and then actually using them to get work done./ Peter Haworth wrote > ....A question in the back of my mind now that I know enough about regexp > to be > dangerous. Is parsing a language something that can be done with regular > expressions? I have a program in which I jumped though all sorts of hoops > to parse SQL statements. It works quite well but maintaining it is a > pain. > It feels like I could use regexps to separate the various "clauses" of a > command, followed by other regexps to parse those clauses depending on > type.... -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Help-with-Regex-was-Re-Switch-Case-and-wild-cards-tp4658429p4658489.html Sent from the Revolution - User mailing list archive at Nabble.com. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
