Re: opening up $cfg to XS

I think the concept is fine. cool. However a few issue with the patch: ok, I'll work on those issues and come up with something better when I have the chance. --Geoff - To unsubscribe, e-mail: [EMAIL PROTECTED] For addition

Re: cvs commit: modperl-2.0/xs/Apache/Module Apache__Module.h

You won't get away with just doing the fun part. fun? :) Can you please update modperl-docs/src/docs/2.0/user/config/custom.pod? Also it'd be very helpful if you have added modperl-docs/src/docs/2.0/api/Apache/CmdParms.pod. At least the part that you have added/changed. I'll try and work on

Re: opening up $cfg to XS

Geoffrey Young wrote: hi again the below patch moves the guts of mpxs_Apache__Module_get_config to a new public function, modperl_get_config, and leaves mpxs_Apache__Module_get_config as a wrapper. a project I'm tinkering with now requires the config object from within XS, but currently I need

Re: $parms->info(), take 2

Geoffrey Young wrote: all those *.h files are full of both mpxs_ functions and static XS functions, with functionaity implemented in one or the other seemingly at random. I have no idea how you would choose one format over the other, but if the mpxs_ implementation makes you more comfortable,

Re: cvs commit: modperl-2.0/xs/Apache/Module Apache__Module.h

[EMAIL PROTECTED] wrote: geoff 2003/05/30 06:37:19 Added: xs/Apache/CmdParms Apache__CmdParms.h Log: implement $parms->info. directive handlers should now be complete. You won't get away with just doing the fun part. Can you please update modperl-docs/src/docs/2.0/user/config/c

Re: cvs commit: modperl-2.0/xs/Apache/Module Apache__Module.h

Geoffrey Young wrote: [EMAIL PROTECTED] wrote: geoff 2003/05/30 06:39:44 Modified:xs/Apache/Module Apache__Module.h Log: sorry, committed a change in progress. really sorry. I'm really sorry about this. I forgot to commit the new directory and file for the $parms->info() st

Re: mp2: segfault in make test on sun4-solaris

[Tulan, you have to keep the thread on the list. Please don't take it off list.] [EMAIL PROTECTED] wrote: Thanks for replying my question. First let's get in sync: Are you using the latest cvs? or mod_perl 1.99? I need to fix the bug report script to include that info. I tried mod_perl 1.99_

Re: a new stacked handlers paradigm

this confusioon actually has bitten a few people and has come up on the list several times. heh, it just showed up (again) today, as a matter of fact :) http://marc.theaimsgroup.com/?l=apache-modperl&m=105432209705846&w=2 --Geoff ---

a new stacked handlers paradigm

hi all... I'd like to talk about the behavior of the stacked handler mechanism in mp2. as we all know, handler return codes mean different things for different phases. for instance, returning OK from a fixup handler in Apache (C modules, this is) lets the next fixup run, while returning O

opening up $cfg to XS

hi again the below patch moves the guts of mpxs_Apache__Module_get_config to a new public function, modperl_get_config, and leaves mpxs_Apache__Module_get_config as a wrapper. a project I'm tinkering with now requires the config object from within XS, but currently I need to copy most of the co