[Gzz-commits] manuscripts/UMLLink short-paper.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuomas J. Lukka <address@hidden>        03/05/29 13:22:18

Modified files:
        UMLLink        : short-paper.rst 

Log message:
        Twids - too long again

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/short-paper.rst.diff?tr1=1.47&tr2=1.48&r1=text&r2=text

Patches:
Index: manuscripts/UMLLink/short-paper.rst
diff -u manuscripts/UMLLink/short-paper.rst:1.47 
manuscripts/UMLLink/short-paper.rst:1.48
--- manuscripts/UMLLink/short-paper.rst:1.47    Thu May 29 12:44:46 2003
+++ manuscripts/UMLLink/short-paper.rst Thu May 29 13:22:18 2003
@@ -94,14 +94,15 @@
 While the class is easily found through the package and class lists
 when looking for a class representing cryptographical public keys,
 the javadoc is not terribly useful: it lacks the information
-there on how to create objects that implement this interface.
-Currently, the only relevant links are on an accompanying ``Use`` page,
-which lists all the references to this interface elsewhere in the 
+on how to create objects that implement this interface.
+The only relevant links are on an accompanying ``Use`` page,
+which lists all the references to this interface in any method 
+prototypes elsewhere in the 
 documentation.
-Further, those lists lack information about the contextual importance of 
-the mentionings --- the methods for 
-creating a ``PublicKey`` are listed alongside eg. the methods
-that return a ``PublicKey`` contained in another object.
+The list does not give information about the contextual importance of 
+the items --- the methods for 
+creating a ``PublicKey`` are listed alongside eg. the accessor methods
+that return a ``PublicKey`` contained in another, unrelated object.
 
 Far more helpful would be a link to the design
 documentation, even just a diagram showing the intended
@@ -206,7 +207,7 @@
 team. Each UML diagram is meant to expose a particular aspect
 of the design. 
 Therefore
-a single program element often appears on several distinct diagrams, 
+a single program element often appears on several separate diagrams
 that 
 together create a multicontext view for the element.