> Frankly, you are never going to achieve good documentation > with no effort. Knowing that something called "blat" is > available is not enough > -- designers need to know what it's for, whether it's a > boolean or a date, etc.
This is true. But this is not meant to be a substitute for good documentation. My efforts are intended to be a substitute for _no_ documentation. And a building block for good documentation. > I think you'd be better off pursuing an approach that makes > it easy for programmers to document what they are sending. Well, it's not this simple, as we'll be using various data sources, some in XML, where the perl "service" is just doing data binding. We don't have the luxury of having consistent documentation for everything that will be offered. I'm doing my best to bridge that gap, and my efforts here are just a first step. - Mark. _______________________________________________ templates mailing list [EMAIL PROTECTED] http://lists.template-toolkit.org/mailman/listinfo/templates
