use Perl

Another reason not to use "ptypes" - you're not replacing the C with Perl, you're replacing the Python with Perl.

I agree with Alias that somehow we should piggy-back off the existing "ctypes" brand, so that (e.g.) when someone googles for "ctypes" they find the new implementation too. I'm not experienced enough with it to know if this is the correct term to piggyback off of, but some pig should be backed.

Do you envision any special-purpose stuff for creating wrapper modules? One thing that's been fairly clear in the Inline::C world is that the needs of people writing wrapper modules & people writing little scripts that call libraries are pretty different.

Very nice work you're proposing. I'd totally use it.

(see title above)

Congratulations to all.

I don't usually have strong design opinions. This time is no exception. =) I like it, and I think it's better than the old site, which was also fine.

I'm glad you chose M::B as an example of usage - it is indeed annoying sometimes to figure out which POD file to look in for what you need.