|
DataMuseum.dkPresents historical artifacts from the history of: Rational R1000/400 Tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about Rational R1000/400 Tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: D T
Length: 1579 (0x62b)
Types: TextFile
Names: »DIRECTIONS_2«
└─⟦180fe333a⟧ Bits:30000405 8mm tape, Rational 1000, SW CATALOG, 10_20_0
└─⟦180fe333a⟧ Bits:30000537 8mm tape, Rational 1000, SW Catalog 10_20_0
└─⟦5cb1d1d7f⟧ »DATA«
└─⟦3b1ee7bd8⟧
└─⟦this⟧
Your next task is to implement the body of the structured comments package
with the additional procedures and write one or more test procedures to
illustrate that it works correctly.
The following interfaces have been provided to help you:
1) package Lines
The Lines package defines a abstraction for a ordered set of
lines of text. It provided interfaces for building up multiple
line objects from single lines of text and for iterating over
all lines in a "Lines" object. If you are not familiar with the
notion of an "iterator" ask your instructor to explain it.
2) function Yeild
This function returns a Lines.Iterator containing the text lines of
the example comment block provided in the Structured_Comments
specification. You may want to build other yeild routines when you
start testing.
You should make maximun use of existing interfaces in the environment.
Do you reimplement functionality you do not have to. You might
want to look through !tools and browse through the interfaces that
are provided there.
Also, before you start, please estimate how much time it will take to do
the following things:
Detailed Design
Coding
Testing
and give the estimates to your instructor.
Also keep track of how much time it actually takes you to do these things.
This is not intended to find out how good you are at solving this problem
but it will tell you something that is very interesting about how much
time it actually takes to do each of these parts of the lifecycle.