Re: [OctDev] Test functions not working?

[David B. <Dav...@mo...>]

According to Josep Mon=E9s i Teixidor <jm...@pu...> (on 09/09/04=
):
> Hi!
>=20
> My computer finally finished building Octave 2.1.58 and Octave-forge an=
d
> I run the tests.
>=20
> I noticed "error" tests don't work... is this only in my copy or is thi=
s
> a known issue?
>=20
> uintlut fails too because it compares 2 uint64 in an assert, which
> doesn't work. Try assert(uint64(1),uint64(1)). Should I comment out thi=
s
> test?

This fails due to the fact that isnan and isinf in octave itself haven't
been converted to accept int/uint args. Or rather the double_value()
method doesn't exist in the integer method. You can see this with the
test case

octave:1> isnan(uint64(1))
error: octave_base_value::double_value (): wrong type argument `uint64 sc=
alar'
octave:2> isnan(uint64([1,1]))
ans =3D

  0  0

So the work around for 2.1.58 is to change your assert to
assert(uint64([1,1]),uint64([1,1])). The really fix is to apply the
attached patch.

> Some days ago I send an email about test don't working ok for int* and
> uint* types (current test doesn't work for int* and uint* scalars, and
> doesn't fail if values in arrays differ),  including a patch. I didn't
> commit it because I'm not 100% sure and this can break a lot of thing,
> specially now.

Could you try the attached patch, it should probably address this issue
too.

D.

--=20
David Bateman                                Dav...@mo...
Motorola CRM                                 +33 1 69 35 48 04 (Ph)=20
Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax)=20
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as:=20

[x] General Business Information=20
[ ] Motorola Internal Use Only=20
[ ] Motorola Confidential Proprietary