Cint(String) Not equal Cint(double)

[pappawinni]

Just tested if I could use Cint() instead of val() to convert a string to integer and
found that e.g.
CInt(-123.123) delivers -123
while
CInt( "-123.123" ) delivers -122
strange, isn't it ?

Same results with CLng

[Slowdown]

To make it more mysterious try,

Cint(val("-123.123")) > result -123

[pappawinni]

Hi Slowdown,

strangely in VBA - even if I got the impression that this is very type tolerant - Cint does not accept string as input.
So you would need to code CInt(Val(string)).

But I think as CInt acceptes String in KBasic it should deliver correct results.

[Slowdown]

Hi pappawinni,
I agree with you, if accepted return the correct value or set an error if it not accept a string.

[tseyfarth]

VB6 did/does accept Cint("123").

I found that I had to change this practice for KB.

Either way is fine, so long as we know what to use, and the results are correct.

Tim

[pappawinni]

Hi Tim,

You - in one case - used int(string) instead of CInt(string) and this is a different story
I told you to use val(string).. because..
Cint() cuts the decimals .. and in Kbasic it accepts string, but for negative values, delivers wrong result.
int() rounds to the next lower Integer... which makes a difference especially for negative values.
Cint(-123.123) delivers -123 while
int(-123.123) delivers -124 ! int() in KBasic does not accept string as input