To gain control/access to a moribund module, keep modules@ up to date on efforts to contact the author. They can alter the commit bits after sufficient effort has been made and time passed.

It looks like Antal's fallen off the grid in March of 2007, but here are some possible leads:

• Older email addresses, the KDE redirect might be live but weevil.net doesn't exist.
• If you know a Stanford alumnus, they might check the alumni directory
• He co-authored two papers with Feng Shao, who has a redirect in the people directory at Cornell and might have kept in touch. He was also co-author on a number of other papers in a variety of other sub-fields… especially computational biology up until August 2009
• Likewise, Antal was co-author of Devel::GDB and the other developer might know something.
• Apparently, there's only one person with this name in US phone books.

You could try to come up with another name for the code, and post the fixed version as a fork, but this should be avoided. A better approach would be to post a patched copy with an underscored version number (developer's copy). It won't show up by default in search.cpan results, but it will still be accessible and until you gain control it can be pointed to in RT tickets, annoCPAN, reviews, this node, etc.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.