C. Michael Pilato wrote:
> Max Bowsher wrote:
>> I'm taking a look at mod_dav_svn, and realizing that a *lot* of the code
>> is focussed on either:
>> (a) implementing various mod_dav vtables
>> (b) sending a particular kind of custom report
>> I have an inclination to refactor the source into the following layout:
> Does this inclination stem from a particular problem you ran into while
> trying to modify mod_dav_svn, or are you just in Tidy-up Mode?
I've found that some of mod_dav_svn's .c files incorporate code that has
little to do with the name of the file - i.e. prime candidates for
splitting chunks of code out into new files.
Rather than pick names for the new files on an ad-hoc basis, the above
schema would help in selecting new names.
Also, many of the files relate to an mod_dav concept, yet are named not
after that concept, but after an abbreviation, expansion, or loosely
Overall, I'd like the file layout to reflect an overall logical
structure, so that a newcomer to the code can quickly understand it, and
then proceed to fill in their knowledge about specific subtopics, rather
than needing study the entire body of code to understand the structure
of how the different source files plug together.
Received on Fri Jul 28 12:10:08 2006