On 01/21/10 00:00, John Jorgensen wrote: > Eric's observation made me think of another suggestion, though > one that would be a lot of work (and I'm not in a position to help > anytime soon)... > > Would it be worthwhile to actually store the resource > descriptions in the *_conf.c files (within comments or maybe even > as part of bacula's runtime help), and then extract those > descriptions to build the documentation? (Something like how > javadoc pulls the API descriptions out of Java source file > comments.) > > Doing so might help prevent divergence between the code and the > documentation as people add new resources or modify the > interpretation of existing ones.
That sounds like an excellent idea. -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 [email protected] [email protected] [email protected] Renaissance Man, Unix ronin, Perl hacker, Free Stater It's not the years, it's the mileage. ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
