> The surprise comes in just how far reaching the apr_pool_t goes. please:
identify the dependency chain. please. if there's some automated code tools that help do this - i believe that even VC++ may help, here - then all the better. or source navigator, or code warrior, or your own perl scripts, or _something_. please, make an ordered tree of data structures that use-and-depend on apr_pool_t, and then you can decide which bits to target first. if i was working on this project, and i've had experience at doing it the _other_ way with 300,000-line codebases, where everybody needs to know what's going on in order to approve it, this is what i would do. the other way, btw, is just to sit in front of a screen 10x7 for 4 weeks and morph the code into submission [ala extreme programming]. this tends to get results very fast and leaves everyone else gawping - and nervous, 'cos it look _nothing_ like it used to. luke
