KSpread: breaks in internal tests

Tomas Mecir wrote:
> The problem with the remaining tests is that a wrong
Value constructor
> is being called, for a reason unknown to me.
> Value("bah") calls the Value(bool b)
constructor, with b=TRUE. Value
> (QString("bah")) works well.
> I think that unless someone has any idea as of why that
wrong
> constructor gets called, I'll just add the QString
re-typing.
> Or we could mark the bool constructor as explicit, that
might help.
 
Maybe not related;
QVariant itself defines QVariant(bool,int) where the second
int is a dummy 
(so, it's needed to say new QVariant(True,0)) cause else
QVariant(int) got 
called even if you say explicit new QVariant(True). So, bool
is a bit tricky 
in that case cause bool is also an int. I could imagine same
goes for char* 
cause it's just an int too...

-- 
Sebastian Sauer aka dipesh[sebsauer]
http://www.dipe.or
g/public_key.asc
Fingerprint: 8F1E 219B 16E6 4EC7 29CC F408 E193 65E2 9134
2221
Coder in http://www.koffice.org
&& http://www.kmldonkey.org
_______________________________________________
koffice-devel mailing list
koffice-develkde.org
h
ttps://mail.kde.org/mailman/listinfo/koffice-devel