While it is possible for people to write modular functions with C, generally it is a pain in the arse because you end up having to pass heaps of parameters and pointers around. It's because of this that people write functions in C that are way too long. CWEB removes that pain because the code from each module is inserted straight into the function where it belongs, so CWEB encourages people to write short modules.

From what you wrote it seems that you are doing a javadoc style system, is that right? Javadoc never produces good code because it encourages people to do a oneliner about the function. CWEB on the other hand provides a place for you to set out your thoughts before starting each modules. I've found that I just started automatically writing down my thoughts in the comment section and then revising it with my new ideas before even writing a single line of code. Given that this comment will be fairly general this also encourages making the code even more modular. When writing the code I just naturally now insert a @<...@>; where some more thought needs to be put into that section of code.

What I'm trying to say is that, for me, CWEB isn't about writing a book. It's about a new method of programming that ensures that your code is highly modular and well documented as well as ensuring that you straighten out your thoughts before writing code. I just don't see those benefits in javadoc style systems.