>
> 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 really nice (also still a lot of work until I can use
it), but I found that when I don't specify the package where to put
functions in, WrapXS makes really strange guesses. It mostly takes the
return type, which doesn't make much sense to me. (For example function in
mod_dav often return a dav_error struct, so all these functions will go into
the Apache::DAV::Error package). The source is the function
*::TypeMap::first_class:
sub first_class {
my($self, $func) = @_;
return $func->{return_type} if $func->{return_type} =~ /::/;
for my $e (@{ $func->{args} }) {
next unless $e->{type} =~ /::/;
#there are alot of util functions that take an APR::Pool
#that do not belong in the APR::Pool class
next if $e->{type} eq 'APR::Pool' and $func->{name} !~ /^apr_pool/;
return $e->{type};
}
return $func->{name} =~ /^apr_/ ? 'APR' : 'Apache';
}
which returns the return_type if it is an object. From my point of view the
return ... if in line 4 should be removed, but I guess it is/was good for
something ?
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
