Yes I definitely agree with this.

Putting the code in an .html file is a nice feature for demo programs

that get posted on web sites, but it doesn't work so well for pure

documentation. I don't know if the people that mentioned this have

tried javadoc or doxygen, but creating documentation from source code

and embedding source code in .html are just two completely different

things. I don't see myself typing all the .html to create fancy layout

like above when writing a .d program. Also Javadoc and Doxygen create

hierarchical structures of your classes, summary and index files,

links from one class to the others that are mentioned and to its

parents, etc, etc, etc. Am I supposed to do this all by hand?

 

Even if I was willing and capable of doing all this by hand, I could

never benefit from other people using it to and all formats would be

radically different.

 

Just search the web for Java documentation. Notice how it is all

uniform and looks alike? This is because all this documentation is

generated using Javadoc. The 'embed d code in a .html file' technique

is not an option for documentation generation.

 

--
Stijn
OddesE_XYZ@hotmail.com
http://OddesE.cjb.net