Excerpts from the mail message of Steven N. Hirsch:
)
) I'd love to see community efforts put towards more complete documentation
) of the Perl C API. Like many others, I've got my little subset of
) routines which I understand fairly well. However, I'm sure there are some
) very handy gems hiding in the source code that I'm unaware of. A push to
) flesh out the Perlguts document would benefit both groups.
Most cases I've seen of people using _more_ of the Perl C API
have been disappointing. For one thing, when something in the
API changes, all of the Perl code gets updated but no one goes
finding all of the modules that use the changed bits and fix
them.
Also, most of the C API is rather entagled so that things that
are simple in C don't work in lots of only-slightly-unusual cases
of real Perl code. So you end up with XS APIs that don't work
in the face of tie()ing or "magic" (or even simpler cases).
So I think more encouragement for using the Perl C API is probably
a bad thing.
--
Tye McQueen Nothing is obvious unless you are overlooking something
http://www.metronet.com/~tye/ (scripts, links, nothing fancy)
