On Fri, 4 Jan 2008 07:44:44 -0800 (PST)
rstupek <[EMAIL PROTECTED]> wrote:
>
> Has anyone with commit priviledges gotten a chance to look at this?
> I would fix it but I don't believe it would be a simple change
>
> rstupek wrote:
> >
> > I've found a bug in TextLineDecoder. The following will not be
> > correctly interpreted by the decoder using \r\n as the LineDelimiter
> >
> > This is some text\r\r\n
> >
> > I believe the issue is that the decoder encounters the first \r and
> > is not able to match because the second character is not a \n but
> > it then has skipped the second \r for purposes of matching the next
> > character which is a \n
> > ...
> > byte b = in.get();
> > if (delimBuf.get(matchCount) == b) {
> > ...
> >
>
Hi
I found the bug, I'll commit a fix soon.
Thanks for the bug report.
Julien