From a0f62b254af5e5a83dfbd1a14ca0bdf8b2d1c686 Mon Sep 17 00:00:00 2001 From: Sami Vaarala Date: Thu, 16 Jan 2014 16:39:22 +0200 Subject: [PATCH] rename test-dev-bug-xxx refs to test-bug-xxx --- doc/testcases.txt | 2 +- src/duk_js_call.c | 2 +- src/duk_js_compiler.c | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/testcases.txt b/doc/testcases.txt index f84c4c2b..cdb60473 100644 --- a/doc/testcases.txt +++ b/doc/testcases.txt @@ -154,7 +154,7 @@ there is currently no tracking of specification coverage. Test cases starting with ``test-dev-`` are development time test cases which demonstrate a particular issue and may not be very well documented. -Test cases starting with ``test-dev-bug-`` illustrate a particular +Test cases starting with ``test-bug-`` illustrate a particular development time bug which has usually already been fixed. Duktape API test cases diff --git a/src/duk_js_call.c b/src/duk_js_call.c index 3c17c57e..ad087f8a 100644 --- a/src/duk_js_call.c +++ b/src/duk_js_call.c @@ -1797,7 +1797,7 @@ void duk_handle_ecma_call_setup(duk_hthread *thr, * Although the callstack entry is reused, we need to explicitly unwind * the current activation (or simulate an unwind). In particular, the * current activation must be closed, otherwise something like - * test-dev-bug-reduce-judofyr.js results. + * test-bug-reduce-judofyr.js results. */ DUK_DDDPRINT("is tailcall, reusing activation at callstack top, at index %d", diff --git a/src/duk_js_compiler.c b/src/duk_js_compiler.c index 10ba7e27..bd0d0e04 100644 --- a/src/duk_js_compiler.c +++ b/src/duk_js_compiler.c @@ -4582,7 +4582,7 @@ static void parse_switch_statement(duk_compiler_ctx *comp_ctx, duk_ivalue *res, * Note that there may be no code at all, not even an empty statement, * between case clauses. This must be handled just like an empty statement * (omitting seemingly pointless JUMPs), to avoid situations like - * test-dev-bug-case-fallthrough.js. + * test-bug-case-fallthrough.js. */ num_stmts = 0; @@ -4974,7 +4974,7 @@ static void parse_try_statement(duk_compiler_ctx *comp_ctx, duk_ivalue *res) { * within the catch clause work correctly. This restriction should * be fixable (at least in common cases) later. * - * See: test-dev-bug-catch-binding-2.js. + * See: test-bug-catch-binding-2.js. * * FIXME: improve to get fast path access to most catch clauses. */