From: MenTaLguY <mental@...>
Date: 2007-03-21T08:10:17+09:00
Subject: Re: [ANN] fastthread 1.0

--=-NuvcNRti0PW6Ne9jDnuk
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, 2007-03-20 at 23:42 +0900, Joel VanderWerf wrote:
> fastthread.c: In function =E2=80=98wait_condvar=E2=80=99:
> fastthread.c:626: warning: passing argument 1 of =E2=80=98rb_ensure=E2=80=
=99 from=20
> incompatible pointer type

Yes, that's harmless in this case.

> Do you happen to have a test case that reproduces the problems in the=20
> pre 1.0?

Not offhand.  I think some of the tests which were added to ruby_1_8
cover the problems though.

> Is there something ruby code can easily do (easier than running the test=20
> case, that is) to detect whether it is running with the patched=20
> fastthread or the buggy one?

The best thing to do is simply to require fastthread if it is available:

 begin
   require 'fastthread'
 rescue LoadError
 end

The fastthread built into 1.8.6 is just "thread".

-mental

--=-NuvcNRti0PW6Ne9jDnuk
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQBGAGnXSuZBmZzm14ERAh+eAKDXa1Pn1+mGItNuCvMJPyq1OBNdAgCgyY3p
/nQotmau31vIIypsp842NIw=
=ttf1
-----END PGP SIGNATURE-----

--=-NuvcNRti0PW6Ne9jDnuk--