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 under which circumstances it makes sense to take the return > type instead of the first argument for guessing the target package of the > function. At the moment I can't imagine a situation where this makes sense, > so I failed to understand the reason why you did it. Because of that I can't > decide how to handle this for the generic situation (mod_dav was only an > example), because the generic code should of course behave in a way to > catches most cases and we override for the specfic ones (of course). If you > have a example function where this takeing of return type makes sense, it > would help me very much.
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'll work on getting rid of that line. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
