Re: source_scan doesn't pick up new MPXS_ method :(

2001-11-27 Thread Stas Bekman
Doug MacEachern wrote: > MPXS_ functions are not supposed to be picked up by source_scan. they are > supposed to be thin wrappers around the real functions that actually do > the work. the real functions are what get picked up by source_scan. that's not the problem. The problem is that the xs

Re: source_scan doesn't pick up new MPXS_ method :(

2001-11-27 Thread Doug MacEachern
MPXS_ functions are not supposed to be picked up by source_scan. they are supposed to be thin wrappers around the real functions that actually do the work. the real functions are what get picked up by source_scan. - To unsubsc

Re: source_scan doesn't pick up new MPXS_ method :(

2001-11-27 Thread Stas Bekman
Gerald Richter wrote: > >>I think I've tried all the combinations of possible ways to declare a >>function in the map file, but in vain -- it won't be picked by the >>source scan. >> >> > > Source scan doesn't look at the maps files at all. Source scan only scans > the h files. Inside of Apache

Re: generating consts

2001-11-27 Thread Doug MacEachern
On Thu, 22 Nov 2001, Gerald Richter wrote: > Hi, > > after having lots of iteration to get the RecDescent parser to not only > most, but all of the Apache functions/structures parsered I am now moveing > to the code generation side. This part I already have abtracted in a common > base class and

Re: mod_perl : no previous prototype for [...]

2001-11-27 Thread Doug MacEachern
On Thu, 22 Nov 2001, Philippe M. Chiasson wrote: > Not sure what just happen, but I started getting this all over the > place: > > gcc -c ... -I/usr/lib/perl5/5.6.0/i386-linux/CORE Base64.c ^ those warnings didn't go away until after 5.6.1 in bleedperl. btw,

Re: source_scan doesn't pick up new MPXS_ method :(

2001-11-27 Thread Gerald Richter
> I think I've tried all the combinations of possible ways to declare a > function in the map file, but in vain -- it won't be picked by the > source scan. > Source scan doesn't look at the maps files at all. Source scan only scans the h files. Inside of Apache/ModPerl::ParseSource there are a

Re: Multiple PostReadRequest handlers

2001-11-27 Thread Stas Bekman
> Ah, I know what's going on. I have one handler defined at the top level > (outside any container) and one defined in that particular . > >> From what I read in mod_perl source, at merge time the latter replaces > > the former. So I guess I should either declare them both at the same level, >

RE: Multiple PostReadRequest handlers

2001-11-27 Thread Eric Cholet
--On mardi 27 novembre 2001 09:53 -0500 Geoffrey Young <[EMAIL PROTECTED]> wrote: >> -Original Message- >> From: Eric Cholet [mailto:[EMAIL PROTECTED]] >> Sent: Tuesday, November 27, 2001 7:53 AM >> To: [EMAIL PROTECTED] >> Subject: Multiple PostReadRequest handlers >> >> >> Is it possib

source_scan doesn't pick up new MPXS_ method :(

2001-11-27 Thread Stas Bekman
I think I've tried all the combinations of possible ways to declare a function in the map file, but in vain -- it won't be picked by the source scan. What I try to add is something like this: Index: xs/maps/modperl_functions.map =

RE: Multiple PostReadRequest handlers

2001-11-27 Thread Geoffrey Young
> -Original Message- > From: Eric Cholet [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, November 27, 2001 7:53 AM > To: [EMAIL PROTECTED] > Subject: Multiple PostReadRequest handlers > > > Is it possible to have several PostReadRequest handlers > run for a request? I have an issue where I

Multiple PostReadRequest handlers

2001-11-27 Thread Eric Cholet
Is it possible to have several PostReadRequest handlers run for a request? I have an issue where I define two of them but only the second one is being run. Maybe this is a matter of the return code of the handlers? This is under mod_perl 1.x/apache 1.x -- Eric Cholet ---