a bug in narcissus parser?

View: New views
4 Messages — Rating Filter:   Alert me  

Parent Message unknown a bug in narcissus parser?

by George-36 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi ,
I happen to find that the narcissus parser seems bearing the following bug
about parsing windows-type end-of-line characters inside JS comments.

In spidermonkey, load narcissus engine by typing *load('js.js')*. Then
execute the following two lines of code.

parse('a=0\x0D\0Aa=1');     // works fine.
parse('/*\x0D\0A*/a=0');   // error: jsparse.js:172: SyntaxError: invalid
quantifier *
                                                   //
 jsparse.js:172: *

Is this a bug of narcissus code? If it is, how can I report this to Mozilla
developers?

Thanks,
Yan Huang
_______________________________________________
dev-tech-js-engine mailing list
dev-tech-js-engine@...
https://lists.mozilla.org/listinfo/dev-tech-js-engine

Parent Message unknown Re: a bug in narcissus parser?

by Blake Kaplan :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Yan Huang <yh8h@...> wrote:
> Is this a bug of narcissus code? If it is, how can I report this to Mozilla
> developers?

Hi Yan,

It looks like this is a bug (I don't see the regexp matcher allowing
backslashes in regexps). Can you report this at bugzilla.mozilla.org in the
"Core" product and the "JavaScript Engine" component?

Thanks.
--
Blake Kaplan
_______________________________________________
dev-tech-js-engine mailing list
dev-tech-js-engine@...
https://lists.mozilla.org/listinfo/dev-tech-js-engine

Re: a bug in narcissus parser?

by Blake Kaplan :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Blake Kaplan <mrbkap@...> wrote:
> It looks like this is a bug (I don't see the regexp matcher allowing
> backslashes in regexps). Can you report this at bugzilla.mozilla.org in the
> "Core" product and the "JavaScript Engine" component?

Uh, of course when I said "RegExp" I meant "comment." Oops.
--
Blake Kaplan
_______________________________________________
dev-tech-js-engine mailing list
dev-tech-js-engine@...
https://lists.mozilla.org/listinfo/dev-tech-js-engine

Re: a bug in narcissus parser?

by George-36 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

It seems not the backslashes in comments were causing the problem. Rather,
it is the carriage-return character '\r' that fails the parser. For example,

parse('/*\n*/a=1'); // parsed just fine

parse('/*\r\n*/a=1'); // fails

Yan Huang

On Sun, Oct 11, 2009 at 4:18 PM, Blake Kaplan <mrbkap@...> wrote:

> Blake Kaplan <mrbkap@...> wrote:
> > It looks like this is a bug (I don't see the regexp matcher allowing
> > backslashes in regexps). Can you report this at bugzilla.mozilla.org in
> the
> > "Core" product and the "JavaScript Engine" component?
>
> Uh, of course when I said "RegExp" I meant "comment." Oops.
> --
> Blake Kaplan
> _______________________________________________
> dev-tech-js-engine mailing list
> dev-tech-js-engine@...
> https://lists.mozilla.org/listinfo/dev-tech-js-engine
>
_______________________________________________
dev-tech-js-engine mailing list
dev-tech-js-engine@...
https://lists.mozilla.org/listinfo/dev-tech-js-engine