-
Notifications
You must be signed in to change notification settings - Fork 0
Emit Better Error Message for Function Declarations in Invalid Locations #19
Comments
There's no other stdout/stderr output collected by the runtests.py script, it could have got lost somewhere, if other output is present on the console, we should log a minor bug against that, too. |
This is our old friend of permitted locations for function declaration syntax. (Thanks @Pasteuriser for confirming.) Classifying as buggy tests. We should emit a better error message in this instance. |
Also tests/test262/ch15/15.4/15.4.4/15.4.4.19/15.4.4.19-5-1.js |
One thing I didn't appreciate before; in ES6, this syntax will be standard-compliant, since FunctionDeclarations can now occur in a block (and the declaration is block-scoped). However, there are some tests here from 2009 and possibly earlier, so I don't think this is a case of eager conformance. |
Yep, I had in the back of my head that they were going to get rid of these sort of discrepancies between the standard and common use (proto, is another example, I believe) It was a bug in the test262 es5 suite, and that's how I've classified it... |
On the conrad-v8-merged branch (I think), latest revision.
The following test cases aborted with a hard crash from somewhere in the parser or its interface.
Quick diagnosis would be appreciated so I can classify the bug or choose to ignore it for the CAV'15 paper writeup.
The text was updated successfully, but these errors were encountered: