Chad wrote:
> Hmm, > After running an example through my head of getting input that is > quoted, I'd have to agree. If I got the string "bob''s" as input I'd want > to get it escaped to "bob''''s" so I could get it properly unescaped back > to its original form. That line of thinking takes me to my next question > for the list... Should an unescape method also be added? As far as I can > tell this method won't run into the same problem as the current escape() > method does (with regards to unescaping), as long as we deal with single > chars for the charsToEscape and escapingChar variables. I personally would want an unescape() method to get back to something approaching my original string in a loss-less fashion. Of course, it wouldn't be perfect as unescape() would likely unescape things that that were escaped prior to calling escape(). Has anyone thought of the requirements for HTML strings? " => " => " & => & => & < => < => < > => > => > -- Michael -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
