> > totalling over 6 million lines of code using a mix of Fortran, C, Tcl
> > and Perl.
And C-shell and ICL scripts.
> > Here's a first stab. Sorry it's a bit rushed. Hope everyone will get a
> > chance to comment before the deadline.
The abstract doesn't have to be polished, just enough to whet the
interest. It's more than adequate already.
> > The Starlink Classic Software Collection (USSC) runs on three different
> > platforms
>
> How about ``until recently targeted at three unix platforms''? Since
> it's in something of a transition, ``runs on three different
> platforms'' is somewhat ambiguous.
I insert a "currently". We did support four at one time, now having
dropped three of those to be replaced by other operating systems. Three
or four is about as many as we can `support' concurrently.
> They will be offered to the main autoconf distribution -- they haven't
> been accepted yet.
Good point, but can be left to the poster itself.
> * I get the impression there's been a payoff for using ADAM. Or is
> that still a theoretical payoff that will allow the Java applications
> to be webservicised easily?
Gosh! You're winding us up. (-:
> * Although the plan was to autoconf everything with minimal changes
> to the code, a certain amount of beneficial refactoring happened anyway
Bugs were found, and bizarre historic anomalies corrected.
> Mmmm, how long's the abstract?
You've almost written the Proceedings paper.
Malcolm
|