You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@perl.apache.org by Stas Bekman <st...@stason.org> on 2003/01/31 05:27:31 UTC

public mod_perl 2.0 C API

As I was exposing mpxs_Apache_request as I needed it in Apache::Peek, I was 
thinking what is the public C mod_perl API. Is that everything that is defined 
in mod_?perl.*\.h and modperl_xs.*\.h files? What about the XS extensions, if 
a 3rd party app wants to use a C function which is not in the core, but in an 
XS extension, how does it get to that header file? Most of those things are 
autogenerated with static functions, so the header file is of no use.

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org


Re: public mod_perl 2.0 C API

Posted by Geoffrey Young <ge...@modperlcookbook.org>.

Stas Bekman wrote:
> As I was exposing mpxs_Apache_request as I needed it in Apache::Peek, I 
> was thinking what is the public C mod_perl API. Is that everything that 
> is defined in mod_?perl.*\.h and modperl_xs.*\.h files? What about the 
> XS extensions, if a 3rd party app wants to use a C function which is not 
> in the core, but in an XS extension, how does it get to that header 
> file? Most of those things are autogenerated with static functions, so 
> the header file is of no use.

hmmm...

over in 1.0 land, there are a few XS macros in mod_perl_xs.h that are of 
use.  in 2.0, there's the C function sv_str_header that I needed to add in 
order to iterate with apr_table_do, which others may find useful as well.

In general, I'd think that the majority of the C and XS stuff would be 
private, with only a few really useful mod_perl functions - most of the 
stuff mod_perl hackers would want is probably ap_* stuff, plus the XS macros 
that make life easier.

how to design it... I dunno :)

--Geoff


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org