From: "Berger, Daniel" <djberge@...>
Date: 2002-06-13T21:40:45+09:00
Subject: RE: Modules and version determination

> -----Original Message-----
> From: Kirk Haines [mailto:khaines@enigo.com]
> Sent: Wednesday, June 12, 2002 3:25 PM
> To: ruby-talk@ruby-lang.org
> Subject: Re: Modules and version determination
> 
> 
> > The two ideas are somewhat orthogonal.  RubyVersion was 
> really just a
> > way of representing the version, so it can easily be 
> compared to other
> > versions.  Kirk's mixin attaches the version to the module, 
> and could
> > easily store the version as a Version object instead of as 
> a string or
> > a float.
> 
> Yes, quite easily.  Right now it accept the version as a 
> string, on the
> assumption that there are few assumptions about version 
> numbers.  I could
> easily change it to store that version, as you say, in a 
> Version object.
> 
> Kirk Haines

Kirk, it sounds like you've thought this out a bit.  Any chance of
publishing something?  It sounds like a good idea.  Once you have something
out there, it's a small step to write a script that generates some stub
documentation and methods automatically when you want to create a new
module, ala Perl's h2xs (ok, slightly different, but hopefully you get the
point).

Anyone care to second my nomination? :-)

Regards,

Dan