--NDin8bjvE/0mNLFQ
Content-Type: multipart/mixed; boundary="4Ckj6UjgE2iN1+kY"
Content-Disposition: inline


--4Ckj6UjgE2iN1+kY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Tilman Sauerbeck [2006-07-29 02:39]:
> Does anyone feel like hacking away at RDoc's regexp horror? ;)

Of course nobody does, so I did it myself.

I attached a patch to fix that problem, please apply so it can go into
ruby 1.8.5.

Regards,
Tilman

--=20
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

--4Ckj6UjgE2iN1+kY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="rdoc-comments-ignore-prototypes.diff"
Content-Transfer-Encoding: quoted-printable

--- parse_c.backup.rb	2005-07-15 17:00:11.001000000 +0200
+++ parse_c.rb	2006-08-09 13:38:24.848954200 +0200
@@ -548,7 +550,7 @@
     def find_body(meth_name, meth_obj, body, quiet =3D false)
       case body
       when %r{((?>/\*.*?\*/\s*))(?:static\s+)?VALUE\s+#{meth_name}
-              \s*(\(.*?\)).*?^}xm
+              \s*(\([^)]*\))\s*\{.*?^\}}xm
         comment, params =3D $1, $2
         body_text =3D $&
=20

--4Ckj6UjgE2iN1+kY--

--NDin8bjvE/0mNLFQ
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFE2hK/27uLisrW2w8RAo98AJ4hxcIO40SCF5TXLmhAaUJGiTCOOACcDV3b
GQkW26WITvZuApZUKUx/ZhE=
=HB0Z
-----END PGP SIGNATURE-----

--NDin8bjvE/0mNLFQ--

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

iD8DBQFE2hK/27uLisrW2w8RAo98AJ4hxcIO40SCF5TXLmhAaUJGiTCOOACcDV3b
GQkW26WITvZuApZUKUx/ZhE=
=HB0Z
-----END PGP SIGNATURE-----