bug report: parser lockup

I've found a trivially reproducible bug:
Message fromString("/* /* */")

I don't have time to study the parser and would be grateful if Quag checks this.

Cheers.

Messages in this topic (1) Reply (via web post) | Start a new topic

.

How's that a bug? You've yet to close the outer comment.

--
Jeremy Tregunna
jtregunna%40blurgle.ca">jtregunnablurgle.ca

On 18-Mar-08, at 4:57 PM, Danya wrote:

> I've found a trivially reproducible bug:
>; Message fromString("/* /* */")
>
> I don't have time to study the parser and would be grateful if Quag
> checks this.
>
> Cheers.
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Messages in this topic (2) Reply (via web post) | Start a new topic

.

Er. On my machine this locks up.

Whether nested comments are supported or not, lock up is not a good thing.

Messages in this topic (3) Reply (via web post) | Start a new topic

.

On 18 Mar 2008, at 01:57 pm, Danya wrote:

> I've found a trivially reproducible bug:
>; Message fromString("/* /* */")
>
> I don't have time to study the parser and would be grateful if Quag
> checks this.

Yes, this used to be in the issue tracker until someone decided to
delete all the issues. When we move to github, maybe we can use their
bug tracker.

Messages in this topic (4) Reply (via web post) | Start a new topic

.

Ah, I see now.

Anyway, I spent now the ten minutes it deserved. Patch is attached.

(I also stumbled upon a couple of undocumented methods in Map and
created docstrings, attached too).

Messages in this topic (5) Reply (via web post) | Start a new topic

.