Open GoogleCodeExporter opened 8 years ago
Would you be willing to submit a patch that contains the unit test to
demonstrate the behavior, as well as the
correction to the line of code you indicated about?
The new unit test should show that scenario 1b is currently failing, and then
after making the change to the
tokenizer the test (and all other pre-existing tests) should pass.
Original comment by darron.schall
on 6 Jan 2010 at 2:42
You actually already have a test for it:
http://code.google.com/p/as3corelib/source/browse/trunk/tests/src/com/adobe/seri
alization/json/JSONTest.as#115
This test should fail currently. I do not have Flex Builder nor FlexUnit, so I
cannot
verify with the proper setup. But if I write:
JSON.decode( "\"\\u0061\"" )
It throws a runtime-error at me, so that test should definitely fail in any
setup.
Could you please execute this test in your local setup? Maybe there is a
problem with
the test-case not catching the error properly, and thus it seems like the whole
test-case works as it never asserts some false.
But in fact the function testDecodeStringWithInvalidUnicodeEscape throws an
error.
Original comment by morten.b...@gmail.com
on 11 Jan 2010 at 3:52
Original issue reported on code.google.com by
morten.b...@gmail.com
on 6 Jan 2010 at 10:22