RE: Modules, Versioning, and Beyond

2001-07-30 Thread NeonEdge
Some random thoughts on versions: 1.> One should not be able to install Alpha and Beta modules into the standard library path without SPECIFICALLY indicating it (--INSTALLBETA). If the option isn't given, then it installs the module in ./blib/ ('use blib'). 2.> 'use strict' and '-w' should

Re: Modules, Versioning, and Beyond

2001-07-30 Thread Dan Sugalski
At 12:48 PM 7/29/2001 -0400, Bryan C. Warnock wrote: >I've been contemplating this off and on for a while now, but the lack >of a Grand Unified Theory of Module Versioning has always led me to >shelve whatever thoughts I may have had to the back of my mind - or to >/dev/null. There was a lot of p

Re: Modules, Versioning, and Beyond

2001-07-30 Thread Bryan C . Warnock
On Monday 30 July 2001 07:07 pm, Dan Sugalski wrote: > FWIW, the interpreter will treat the following three things (Barring > changes from Larry) as composing a unique identifier: > > Module Name > Author > Version > I originally said I thought choosing by author to be a bad choice.

Re: Modules, Versioning, and Beyond

2001-07-29 Thread John Siracusa
On 7/29/01 12:48 PM, Bryan C. Warnock wrote: > Let's just arbitrarily assume that the > major number of the version is equivalent to that version of the API. > (In other words, Foo 1.05 gives us a promise that it uses the same API > as 1.02 and 1.08. Foo 2.01 would use a different (however slight