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.
This commit is contained in:
Daniel Hensby 2013-11-13 10:49:55 +00:00
parent bedf292612
commit be4ff501f7

View File

@ -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);
}
}