From be4ff501f7c8788f4e49fc58a711cc55f3da76e0 Mon Sep 17 00:00:00 2001 From: Daniel Hensby Date: Wed, 13 Nov 2013 10:49:55 +0000 Subject: [PATCH] Making ConfigStaticManifest::parseStatic error more meaningful The error thrown by `parseStatic` when there's an unexpected token is now more meaningful as it states the type of token that was encountered as well as the class that it was found in. --- core/manifest/ConfigStaticManifest.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core/manifest/ConfigStaticManifest.php b/core/manifest/ConfigStaticManifest.php index 62185bad3..7583dae42 100644 --- a/core/manifest/ConfigStaticManifest.php +++ b/core/manifest/ConfigStaticManifest.php @@ -282,7 +282,7 @@ class SS_ConfigStaticManifest_Parser { // NOP } else { - user_error('Unexpected token when building static manifest: '.print_r($token, true), E_USER_ERROR); + user_error('Unexpected token ("' . token_name($type) . '") when building static manifest in class "' . $class . '": '.print_r($token, true), E_USER_ERROR); } }