Re: organizing deep source trees with child packages

[Ludovic Brenta <ludovic@ludovic-brenta.org>]

Simon Wright wrote:
> Ludovic Brenta <ludo...@ludovic-brenta.org> writes:
>> Shark8 writes on comp.lang.ada:
>>> Spot on. Having the code be a bunch of versions in a DB would be
>>> fantastic as far as development/searching would be; it would be even
>>> better if the code itself were, for lack of a better phrase, a set of
>>> stored-tokens (instead of plain text) as this would allow different
>>> programmers to apply personalized formatting to the source without
>>> causing (what would be in text-files) a change resulting in another
>>> version.
>
>> Wasn't that how the Rational R1000 machine worked?
>
> Exactly so. Except you didn't get to apply personalised formatting; thus
> eliminating at a stroke a whole class of religious strife.
>
> (Actually, I don't remember what if any VCS style was supported; I never
> got to use it for a real project, just an evaluation, and we hadn't
> heard of VCSs then).

There was a VCS integrated; I used it as part of Rational Apex on
Solaris a few years ago.  I think it was slightly different from the
original, as it used RCS as a storage back-end for source files and
introduced the "subsystem" (consisting of many source files) as the
preferred unit of configuration management.  Branching was OK but
merging was horrible, as with RCS.

The continuous updates of the DIANA database were also gone by then;
the database was only updated on demand as part of compilation.

--
Ludovic Brenta.