note tye <blockquote><blockquote> (And, despite the OP's claim, '*/' in a string literal isn't a problem.) </blockquote> The OP didn't identify the language involved, so I took him at his word. </blockquote> No offense intended, but that's hilarious. If you took them at their word with regard to '*/', then you must not have with regard to '/*'. <blockquote> Seems I don't have the 'I-know-better-than-the-OP' gene that you and several others around here have. I don't miss it. </blockquote> Where did I say a specific language that I was assuming? I guess you have the "You know better than some" gene, since you aren't taking me at my word. That insult is so comical in the face of you presuming that this unspecified language accepts the following for string literals: <c>"(?:\\\\|\\[abfnrt]|\\u[0-9a-fA-F]{4}|\\x[0-9a-fA-F]{2,4}|\\"|[^"])+?"</c>. That is an impressively specific set of features for an unspecified language. I tried to be quite polite. But I am not surprised that you found it so very hard to admit to even a simple mistake that you responded with an attack. Just saddened. The OP didn't say that they are using a language that parses string literals inside of block comments. They certainly didn't say that their language parses string literals only inside of block comments. The idea of there even existing a language where string literals are parsed only inside of block comments is quite humorous. But that is all that your regex tries to handle. But composing the regex 'backward' in that way is quite a simple mistake. The kind of mistake I make all the time. Most people do. I am sorry my correction caused you distress (or seemed to). That wasn't my intent. I would appreciate it if you would at least refrain from responding with another insult. (I thought pointing out the mistake was actually more polite than down-voting and not commenting, something you've complained about repeatedly.) <div class="pmsig"><div class="pmsig-22609"> - [tye]<tt>        </tt> </div></div> 996552 996585