[r6rs-discuss] Rationale issues

From: Mikael Tillenius <mti>
Date: Thu, 28 Jun 2007 23:29:21 +0200

AndrevanTonder escribi?:
> Not to mention unmodular. Each time I check in an update of a library
> in a large project an obtain a stable release,
> am I to update the source of all 43 dependent libraries to
> reflect this? And once I update them, how about the 43
> libraries that depend on each of these?
>
> There are good versioning tools that keep things consistent
> on a higher level than the source of the stuff being kept
> consistent, are free, and are in common use in the industry.
> Anyone in his right mind who does projects large enough to
> need version control will already be using one of these.

My understanding is that the versions are mainly supposed to be used for
_releases_ of libraries, not during internal development.

And you shouldn't normally import a specific version of a library, only
specify the lowest required version. Then you don't have to update your
source files except when you modify them anyway to use new features from
the library.

At least thats how I would use versions.

/Mikael
Received on Thu Jun 28 2007 - 17:29:21 UTC