From eaea40b33721513d4c0228af92d5c32400fda0e7 Mon Sep 17 00:00:00 2001 From: Philipp Stephani Date: Tue, 23 Apr 2019 16:48:49 +0200 Subject: [PATCH] Use high-level integer conversion macro in a few cases. MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit INT_TO_INTEGER is more obviously correct and means we don’t have to worry about data type sizes and signedness. * src/json.c (json_parse_error): Use INT_TO_INTEGER. The tiny performance gain of make_fixed_natnum isn’t worth the trouble then signaling an error. --- src/json.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/json.c b/src/json.c index 7d6d5314270..03468e9f338 100644 --- a/src/json.c +++ b/src/json.c @@ -304,8 +304,8 @@ json_parse_error (const json_error_t *error) #endif xsignal (symbol, list5 (json_build_string (error->text), - json_build_string (error->source), make_fixed_natnum (error->line), - make_fixed_natnum (error->column), make_fixed_natnum (error->position))); + json_build_string (error->source), INT_TO_INTEGER (error->line), + INT_TO_INTEGER (error->column), INT_TO_INTEGER (error->position))); } static void -- 2.39.2