Skip to content

Updated the "Why regexes are bad..." section #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Updated the "Why regexes are bad..." section #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions s/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,12 +8,18 @@ are inadequate for the job. You should use an HTML parser.

This site shows you how.

# Why **regexes** are bad for **HTML parsing**

* [This answer on stackoverflow](http://stackoverflow.com/questions/1732348/regex-match-open-tags-except-xhtml-self-contained-tags/1732454#1732454) is a good starting point.
* [This post by Tom Christiansen](http://stackoverflow.com/questions/4231382/regular-expression-pattern-not-matching-anywhere-in-string/4234491#4234491) shows that **you can parse HTML with regex**. The solution is neither easy to comprehend/debug/extend nor practical when you have dedicated libraries to do the **HTML parsing** as alternatives.



# To do

* Add more languages.
* Explain why regexes are bad.
* Explain how fragile regexes are.
* More explanations of why regexes are bad.
* More explanations of how fragile regexes are.

# Thanks

Expand Down