I'm a little iffy on moving the set operation section to before the classes (and the methods they use) are documented.  I'd be more comfortable leaving that after.  There's also a section on sorting that I gave to David that really should be at the end, so it will have company.


On 7/25/07, Rony G. Flatscher <Rony.Flatscher@wu-wien.ac.at> wrote:
Hi David,

To clarify what I am proposing I created a version of the docs that has my proposed organization.


The only difference is in the organizations of the collection classes section.

Please let me know what you think.

How about:

5.3. The Collection Classes
5.3.1 General Concepts of Collection Classes Classifying Collections Setlike Operations on Collections Hierarchical Overview of the Collection Classes
5.3.2 Collection Classes Ordered by Name The Array Class Inherited Methods Defined Methods new (Class Method) of (Class Method) []
... Sorting Arrays Examples The Bag Class
... The Table Class
  • Created a new heading at the "Inherited Methods" level, entitled "Defined Methods"; all locally defined methods are then listed a level deeper
    • for the Array class moved "5.3.17. Sorting Arrays" to " Sorting Arrays", aligned at the same hierarchy level as " Inherited Methods", " Defined Methods" and finally moved " Examples" to " Examples" (aligned with "Inherited Methods" etc.)
    • would suggest introducing "5.3.2.x.2 Defined Methods" in all classes, examples should be moved to level "5.3.2.x.4 Examples"
  • moved "5.3.18. The Concept of Set Operations" to " Setlike Operations on Collections"


This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
Oorexx-devel mailing list