Re: TiPool: chicken and egg callback problem/question

On Mon, Mar 11, 2002 at 01:46:57PM -0800, Doug MacEachern wrote: > On Tue, 12 Mar 2002, Philippe M. Chiasson wrote: > > > MPXS_tipool_foo(modperl_tipool_t *tp) > > might be better to make that SV *tp, then you can just do: > > PUSHMARK(sp) > XPUSHs(tp); > PUTBACK; > retval = call_sv(...);

Re: regional mod_perl mailing lists?

Hi I'm running Japanese mod_perl mailing list. http://bulknews.net/lib/ml/ This list is working on a free mailing list service called "freeml" in Japan. At Tue, 12 Mar 2002 11:16:16 +0800, Stas Bekman wrote: > > I was thinking today about the possibility of regional mod_perl > > mailing lis

Re: regional mod_perl mailing lists?

Geoffrey Young wrote: > I was thinking today about the possibility of regional mod_perl > mailing lists - kinda like the way local perl mongers have their own > lists to coordinate group activities, post local jobs, and just keep in > touch with others in their area with similar interests. T

regional mod_perl mailing lists?

hi all... I was thinking today about the possibility of regional mod_perl mailing lists - kinda like the way local perl mongers have their own lists to coordinate group activities, post local jobs, and just keep in touch with others in their area with similar interests. before posting a

Re: TiPool: chicken and egg callback problem/question

On Tue, 12 Mar 2002, Philippe M. Chiasson wrote: > MPXS_tipool_foo(modperl_tipool_t *tp) might be better to make that SV *tp, then you can just do: PUSHMARK(sp) XPUSHs(tp); PUTBACK; retval = call_sv(...); - To unsubscrib

Re: [patch] more flexible types declaration in typemap

On Tue, 12 Mar 2002, Stas Bekman wrote: > You don't like allowing this too?: > > char *| foo | ... oh, i didn't realize it prevented that. make whatever changes for better alignment. i just prefer 'type * |' rather than 'type *|' --

TiPool: chicken and egg callback problem/question

I am almost done with my tipool implementation, and I just ran into this little thing I had left for later. How can I do this? I am inside an XS function, and I must call a perl-land sub, no problem. But as an argument to that perl fuction I must pass a reference to the object in question. i.e.

Re: [patch] more flexible types declaration in typemap

On Mon, Mar 11, 2002 at 07:54:44AM -0800, Doug MacEachern wrote: > On Mon, 11 Mar 2002, Stas Bekman wrote: > > > in any case C allows you to say 'type *' why WrapXS shouldn't. > > yeah but we don't do that. 'type *' is the code style, why invent a > different style for the .map files? stick

Re: [patch] more flexible types declaration in typemap

Doug MacEachern wrote: > On Mon, 11 Mar 2002, Stas Bekman wrote: > > >>in any case C allows you to say 'type *' why WrapXS shouldn't. >> > > yeah but we don't do that. 'type *' is the code style, why invent a > different style for the .map files? stick with the enforced style please. I ag

Re: [patch] more flexible types declaration in typemap

On Mon, 11 Mar 2002, Stas Bekman wrote: > in any case C allows you to say 'type *' why WrapXS shouldn't. yeah but we don't do that. 'type *' is the code style, why invent a different style for the .map files? stick with the enforced style please. --

Re: [patch] more flexible types declaration in typemap

Stas Bekman wrote: > this patch is to flex things a bit, so the entries in typemap can be > aligned for an easier human consumption. Currently this doesn't work: > > unsigned long:DEFINE_conn_count | | modperl_worker_score_t *:self > char*:DEFINE_client | | modperl_worker_score_t *

[patch] more flexible types declaration in typemap

this patch is to flex things a bit, so the entries in typemap can be aligned for an easier human consumption. Currently this doesn't work: unsigned long:DEFINE_conn_count | | modperl_worker_score_t *:self char*:DEFINE_client | | modperl_worker_score_t *:self the patch allows thi