Re: Version numbering scheme and language sup****t

On May 8, 7:57=A0pm, James Harris <james.harri...@[EMAIL PROTECTED]
> wrote:
> Is there any mileage in devising a general application version
> numbering scheme and providing sup****t this in a programming language?
> The reason for asking is that it seems useful, in terms of managing a
> computer system composed of many modules, for the components of that
> system to have at least
>
> =A0 =A0<user version info>.<feature>.<fix>
>
> where
>
> =A0 =A0<feature> increments on each /release/ of a new feature set
> =A0 =A0<fix> resets to 0 or 1 on each feature change and increments on
> each released bug-fix
>
> The user version info would be arbitrary so could include higher level
> version numbers or not as needed. For example, MyApp.2.1.4 would be a
> release of "MyApp.2" feature set 1 and fix version 4.
>
> Why offer sup****t for this in a programming language? For two reasons,
> 1. it provides intrinsic sup****t for releases of standard (and
> possibly other) libraries for the language; 2. it offers this sup****t
> to applications (and system programs) written in the language. These
> are only worth doing if the scheme is general enough.
>
> Note that use of the scheme would be optional for apps and system
> programs, and strictly speaking optional for libraries too. I'm not
> proposing mandating use of this feature, just asking if it would be
> useful and if there is a better way to arrange releases of code.
>
> --
> James

Perl has something like this.  http://perldoc.perl.org/functions/use.html