Change 'Parse error' to three more informative messages.

Change 'Parse error' to three more informative messages.

Replace the 'unable_to_parse' key used in three places with three difference keys.
Provide three more informative and less ambiguous error messages in place of 'Parse error'.

Add three test/message cases to cover the new messages.

BUG=2636
Committed: https://code.google.com/p/v8/source/detail?r=14462

[johnjbarton, 2013-04-17 17:36:26]

I did not add tests...can you point me to where the parse errors are tested?

[mvstanton, 2013-04-22 12:32:30]

On 2013/04/17 17:36:26, johnjbarton wrote:
> I did not add tests...can you point me to where the parse errors are tested?

Hi John,
Looks like the right place to add a test for this is in test/message. You can
provoke the parse error you want, then verify that the output matches a certain
form.

The change looks good, add that test and send it back to me, thanks!
--Michael

[johnjbarton, 2013-04-22 15:17:55]

On 2013/04/22 12:32:30, mvstanton wrote:
> Looks like the right place to add a test for this is in test/message. You can
> provoke the parse error you want, then verify that the output matches a
certain
> form.

test/message seems to have only JS-caused messages. The cases I have are all
about source from C++, eg source from an embedder. Are there tests for JS coming
from C++?

[johnjbarton, 2013-04-25 17:19:43]

Ok, ready for review

[mvstanton, 2013-04-26 14:25:33]

lgtm. I'll submit the patch...

[mvstanton, 2013-04-26 14:27:07]

Committed patchset #4 manually as r14462 (presubmit successful).