From c5ee08d809bba566ef9ef4bea3c50c901e1c5c19 Mon Sep 17 00:00:00 2001 From: Tor Lillqvist Date: Mon, 23 Nov 2015 08:55:35 +0200 Subject: Change comment to match reality See include/vcl/devicecoordinate.hxx. (But why do we use the vague 'long' and not sal_Int32? Note that 'long' is not necessarily any "longer" than 'int', so if we don't want to use (the admittedly ugly-looking) 'sal_Int32', why not simply 'int'?) Change-Id: I8d27b43b64eaed86dd95eb89866db8d5680cc60b --- config_host/config_vcl.h.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'config_host/config_vcl.h.in') diff --git a/config_host/config_vcl.h.in b/config_host/config_vcl.h.in index 01d2cfdc59aa..81419d2c0ded 100644 --- a/config_host/config_vcl.h.in +++ b/config_host/config_vcl.h.in @@ -6,8 +6,8 @@ Settings about vcl #ifndef CONFIG_VCL_H #define CONFIG_VCL_H -/* nature of the device pixel coordinate system - * either use sal_Int32 or double for coordinates +/* Nature of the device pixel coordinate system. + * We either use long or double for coordinates. */ #define VCL_FLOAT_DEVICE_PIXEL 0 -- cgit