37 |
http://www.cis.ksu.edu/~hankley/d841/Fa99/chap2.htm |
http://www.cis.ksu.edu/~hankley/d841/Fa99/chap2.htm |
38 |
http://www.computer.org/proceedings/apsec/0915/09150206abs.htm?SMSESSION=NO |
http://www.computer.org/proceedings/apsec/0915/09150206abs.htm?SMSESSION=NO |
39 |
|
|
40 |
http://www.computer.org/software/so1994/s4104abs.htm |
http://www.computer.org/software/so1994/s4104abs.htm |
41 |
|
|
42 |
Abstract |
Abstract |
43 |
======== |
======== |
62 |
.. Since these parts of documentation are semantically dependent |
.. Since these parts of documentation are semantically dependent |
63 |
they should be interlinked together. |
they should be interlinked together. |
64 |
|
|
65 |
While the generation of easily navigable hypertext |
The generation of easily navigable hypertext |
66 |
from the embedded documentation is essentially |
from the embedded documentation is essentially |
67 |
a solved problem |
a solved problem |
68 |
for several languages |
for several languages |
69 |
[friendly95javadoc-andalso-heesch03doxygen-andalso-devanbu99chime]_, |
[friendly95javadoc-andalso-heesch03doxygen-andalso-devanbu99chime]_. |
70 |
the connection to design documentation has been more elusive. |
|
71 |
|
|
72 |
.. There exist plenty of documentation tools to generate well navigable |
.. There exist plenty of documentation tools to generate well navigable |
73 |
documentations from program code source files. Altough, many of |
documentations from program code source files. Altough, many of |