Re: ParseSource etc.

2001-10-07 Thread Gerald Richter
> > > These two things would need a extention of the xxx_types.map files. I would > > suggest simply append two addtional (optional) parameters for each line. The > > first holds the name used in the typemap file (%typemap) and the second the > > alias for the sv_convert.h file (%convert) > > all

Re: ParseSource etc.

2001-10-07 Thread Doug MacEachern
On Sun, 7 Oct 2001, Gerald Richter wrote: > I think we could easily remove this line and put the package name for these > three functions in the map file. That would make much more sense to me. If > you agree to that, I will do it and you don't have to take care about it. already taken care of

Re: ParseSource etc.

2001-10-07 Thread Gerald Richter
> > putting some trace statements in there, there's only 3 places where > return_type is actually used: > using Apache::Filter for ap_add_input_filter > using Apache::RequestRec for ap_read_request > using APR::IpSubnet for apr_ipsubnet_create > > i suppose we could probably get by without it, i'l

Re: ParseSource etc.

2001-10-07 Thread Doug MacEachern
On Sun, 7 Oct 2001, Gerald Richter wrote: > I do that anyway, because the first_class method contains other Apache > specific things (like checking for pool). I have done this in many places to > spearate generic code from mod_perl specific. The difference here is, that I > don't understand unde

Re: ParseSource etc.

2001-10-07 Thread Gerald Richter
> > > sub first_class { > > couldn't you just override this method to make it do what works best for > dav? > I do that anyway, because the first_class method contains other Apache specific things (like checking for pool). I have done this in many places to spearate generic code from mod_perl spe

Re: ParseSource etc.

2001-10-06 Thread Doug MacEachern
On Sat, 6 Oct 2001, Gerald Richter wrote: > sub first_class { couldn't you just override this method to make it do what works best for dav? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL P

Re: ParseSource etc.

2001-10-06 Thread Gerald Richter
> > if it makes things easier to run through cpp first, by all means do. I will rethink what's the best solution Another question. I have gotten very far in separting the mod_perl specific code and the generic code. So I tried to run what I have so far over mod_dav 1.x and the result is real

Re: ParseSource etc.

2001-10-05 Thread Doug MacEachern
On Fri, 5 Oct 2001, Gerald Richter wrote: > I've done so, but it's hard work to get all the details right, so it's still > under construction, also the results already comes very close to the tables > in the CVS. great!! > There is one issue I like to get some feedback before continuing. C::S

Re: ParseSource etc.

2001-10-04 Thread Gerald Richter
> > I have played along this line a few hours, taken the grammer from Inline::C > and Inline::Struct and now have a nearly working replacement for C::Scan. I > think this is the right way to go, since the RecDecent parser grammer is > much easier to extent and modify (and it works on all platforms

Re: ParseSource etc.

2001-09-27 Thread Doug MacEachern
On Thu, 27 Sep 2001, Gerald Richter wrote: > I have played along this line a few hours, taken the grammer from Inline::C > and Inline::Struct and now have a nearly working replacement for C::Scan. I > think this is the right way to go, since the RecDecent parser grammer is > much easier to exten

Re: ParseSource etc.

2001-09-27 Thread Gerald Richter
Doug, > gerald, i would be happy to see the source parser usable outside of > modperl. first i would like to solve the C::Scan problem. it just isn't > usable on every system. Agreed > i think one option would be to ditch C::Scan and > see if Parse::RecDecent can be used in place of it. i

Re: ParseSource etc.

2001-09-26 Thread brian moseley
you gotta figure that *::gramar.pm are generally useful (think of lxr) and deserve their own namespace and packaging. On Wed, 26 Sep 2001, Doug MacEachern wrote: > gerald, i would be happy to see the source parser usable outside of > modperl. first i would like to solve the C::Scan problem. i

Re: ParseSource etc.

2001-09-26 Thread Doug MacEachern
gerald, i would be happy to see the source parser usable outside of modperl. first i would like to solve the C::Scan problem. it just isn't usable on every system. i think one option would be to ditch C::Scan and see if Parse::RecDecent can be used in place of it. i looked at Inline.pm, they h

ParseSource etc.

2001-09-25 Thread Gerald Richter
Hi, some time ago we discussed to make ParseSource and the other XS generation modules more generic. My goal is to also use them outside of mod_perl. At the moment I like to create a perl wrapper for mod_dav 1.x and don't like to code anything by hand. I also expect using this method will make po