> You are correct. I didn't realize that pflatten was a cheat (plus scary > comment in apr_brigade_pflatten: 'XXX This is dangerous beyond > belief..'). I thought it didn't call apr_brigade_length, but did flatten > at one pass. I should have looked at the source. Sorry about that.
np. I guess we both need to learn to shoot less from the hip... or lighten up a bit :) > Yeah, I did do that initially, but thought that you won't like it, so > I've kept it your way. well, I didn't see a mpxs_usage_va variant that allowed for two object (bb and pool) so I did them both manually. but for one I guess it doesn't matter. >> apr_brigade_pflatten should now get a different modifier than ~ in >> apr_functions.map. > > > why? it's implemented, no? kinda. I guess my thought is that if it has a ~ then it means that it's implemented proper - there's no pflatten() method anywhere now. but the maps are more of a guideline anyway for non-autogenerated stuff, so it's no biggie. at any rate, at least we now have something that works. --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
