Has anyone come across the the issue of unwanted interdependency of documentation and source code releases when embedding documentation in source code?
By this I mean that my documentation is extracted from my RTL source code and the following sequence occurs: 1. My RTL is verified, released and frozen. Prayers have been prayed, sacrifices offered up, and it is done. No more changes. 2. I generate my documentation for the last time, using the frozen RTL as a source, and realise that there is a documentation error in that source. The difficulty is to find a robust process that respects the integrity of the frozen RTL but allows me to make the necessary documentation update. I can imagine some hacks, but does anyone have experience of a good process please? Thanks for any suggestions, Andy Betts ------------------ +33 6 12 19 49 03 skype: betts.crolles www.icondasolutions.com ------------------ ------------------------------------------------------------------------------ LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk _______________________________________________ Doxygen-users mailing list Doxygen-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/doxygen-users
