From 64da969ea30ffba751c0a64d4fbfa4f9ad969adf Mon Sep 17 00:00:00 2001 From: "pschwartau%netscape.com" Date: Fri, 23 Aug 2002 22:48:38 +0000 Subject: [PATCH] Editing comments. git-svn-id: svn://10.0.0.236/trunk@127998 18797224-902f-48f8-a5cc-f745e15eee43 --- mozilla/js/tests/js1_5/Array/regress-157652.js | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/mozilla/js/tests/js1_5/Array/regress-157652.js b/mozilla/js/tests/js1_5/Array/regress-157652.js index a458246f013..f2cdc828bd6 100644 --- a/mozilla/js/tests/js1_5/Array/regress-157652.js +++ b/mozilla/js/tests/js1_5/Array/regress-157652.js @@ -55,8 +55,10 @@ * * * We'll try the largest possible array first, then a couple others. -* Try to be good about memory by nulling each array variable afterwards. -* This will tell the garbage collector the memory is no longer needed. +* We're just testing that we don't crash on Array.sort(). +* +* Try to be good about memory by nulling each array variable after it is +* used. This will tell the garbage collector the memory is no longer needed. */ //----------------------------------------------------------------------------- var bug = 157652; @@ -74,15 +76,15 @@ printStatus(summary); * Note this terminates the test with exit code 1 in Rhino * and exit code 3 in SpiderMonkey. * - * Therefore we include |expectExitCode(n = 1,3)| below. + * Therefore we put |expectExitCode(n = 1,3)| below. * - * The only problem will arise when the JS shell ever DOES + * The only problem will arise if the JS shell ever DOES * have enough memory to do the sort. Then this test will * terminate with the normal exit code 0 and fail. * * Right now, I can't see any other way to do this, because * "out of memory" is not a catchable error: it cannot be - * caught with try...catch. + * trapped with try...catch. */ if (inRhino()) expectExitCode(1); @@ -90,7 +92,6 @@ else expectExitCode(3); - /* * Rhino can't seem to handle the largest array: it hangs... * So we'll skip this case in Rhino -