tag:blogger.com,1999:blog-8252382045298087155.post7945401145142022082..comments2024-03-25T03:49:14.499-07:00Comments on Hey, what smells like blue?: Smart XML Processing with RegexesMike Stonehttp://www.blogger.com/profile/09679171357355203605noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8252382045298087155.post-517484066966524362009-11-24T23:35:50.275-08:002009-11-24T23:35:50.275-08:00Thanks for the comment Noah! I think you reiterat...Thanks for the comment Noah! I think you reiterated my point, or at least the point I had intended to make. That is, think about your problem and what may solve it best, not what someone says to blindly always or never do. Granted, regexes for XML/HTML processing has a completely different tone when the source of the data is known vs unknown, but that doesn't stop the fact that you should always consider your alternatives.Mike Stonehttps://www.blogger.com/profile/09679171357355203605noreply@blogger.comtag:blogger.com,1999:blog-8252382045298087155.post-32998201971001933672009-11-22T19:00:05.966-08:002009-11-22T19:00:05.966-08:00More importantly, you knew where the gigabyte of X...More importantly, you knew where the gigabyte of XML came from, and you were able to do reasonable inspection on it.<br /><br />A lot of Jeff Atwood's advice there comes from web sites, where you spent a lot of time and effort trying to keep attackers from being able to worm past badly-written regexp-based parsers. Fundamentally, parsing known-good data from a trusted source is a whole other world from that.Noah Gibbshttp://blog.angelbob.comnoreply@blogger.com