Re: Make ietf-drums-remove-comments() robust against broken header

["Bjørn Mork" <bmork@dod.no>]

Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>>>>> Bjørn Mork wrote:
>> TSUCHIYA Masatoshi <tsuchiya@namazu.org> writes:
>
>>> I have just met a message including a broken references header, like:
>>>
>>>   References: <200810150047.AA17342@mailhost.example.net>
>>>         <7B77911B-167E-47BF-A826-1C4396FEF000@foo.example.net>
>>>         <7B77911B-167E-47BF-A826-1C4396FEF000@foo.example.net>
>>>         (=?iso-2022-jp?B?IhskQj0pTVUbKEIgGyRCTSdOSRsoQg==?= "'s message of "Fri, 17 Oct 2008 04:32:17 +0900")
>
>> I fail to see how that's broken.  Care to explain?
>
> In the condition where `ietf-drums-syntax-table' is used,
> the parentheses in the last line are unbalanced.  For instance:
>
> (progn
>   (pop-to-buffer "*testing*")
>   (erase-buffer)
>   (insert "(=?iso-2022-jp?B?IhskQj0pTVUbKEIgGyRCTSdOSRsoQg==?= \"'s message of \"Fri, 17 Oct 2008 04:32:17 +0900\")")
>   (require 'ietf-drums)
>   (set-syntax-table ietf-drums-syntax-table)
>   (goto-char (point-min))
>   (forward-sexp 1))

Yes, I can see that the parsing fails, but there's nothing wrong with
the comment, is there?  Any number of "'s are allowed, including odd
numbers.

And won't the suggested patch kill something like this?:

   References: (") <200810150047.AA17342@mailhost.example.net>

which AFAICS is allowed.  



Bjørn
-- 
Ban the war on drugs