Issac Goldstand wrote: >> >>> For example, I'm attempting to port Apache::Request (bored of waiting >>> on an official release, plus I have nothing better to do today since >>> the file server containing our company's CVS tree crashed last night >>> :) It wants to typemap the Apache::RequestRec and APR::Table >>> objects. It seems odd that modperl would provide the typemap (in >>> PERL_LIB/Apache2/typemap) but then offer no way of linking against >>> the functions necessary for it to be of any use. >> >> >> >> I've ported the c apreq to 2.0 already (posted to the apreq list), but >> you don't need to port the perl part. It'll be automagically created >> by WrapXS (most of it) once it's a part of httpd. >> > > OK - This is seriously bugging me because I keep hearing about WrapXS > and it sounds really neat - but I'm missing some basics - how does it > differ from the existing XS code, what exactly will it do, etc? Can > someone get me started off here?
Gerald has posted his essay here very timely, read his docs and I wrote some docs here, though they aren't complete of course: http://perl.apache.org/release/docs/2.0/devel/core_explained/core_explained.html __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
