> I believe that unescaped \ is an error, and we will fix. > However, I do not see the issue with quotation marks within comments. > WHo cares if they are matched?
Thanks for clarifying that. Of course, there is no strict need to escape quotes in comments. I was thinking of the convenience of the parser-writer: disallowing them would help make the parser seperable into "lexical" and "syntactic" analysis [something RFC2543 referred to explicitly by claiming to be a "word-based protocol", though it qualified this by stating that not all headers will necessarily conform to this]. But if unbalanced qoutes are permitted in comments, such a seperation is more awkward, because it would mean that a recursive (syntactic) structure, [comment] interfered with a lexical structure [quoted string]. Oh well... > It is a guideline, but not a MUST strength recommendation, for headers > to have the general form that uses comma as an element separator. You > should not be deeply parsing any headers for which you don't know about, > so I don't really see an issue. My question about comma-seperators was also motivated from convenience of parsing: I wondered if it was legitimate to reuse generic code for counting and seperating the fields of an arbitrary header. I see now that this is not possible. Regards, Nick -- Nick Hollinghurst [EMAIL PROTECTED] Research Engineer AT&T Laboratories, Cambridge, England _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
