This is great - thanks Robby.<br><br>yc<br><br><div class="gmail_quote">On Mon, Nov 9, 2009 at 3:44 AM, Robby Findler <span dir="ltr"><<a href="mailto:robby@eecs.northwestern.edu">robby@eecs.northwestern.edu</a>></span> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Check out the version/utils library.<br> <br> Robby<br> <div><div></div><div class="h5"><br> On Mon, Nov 9, 2009 at 4:18 AM, YC <<a href="mailto:yinso.chen@gmail.com">yinso.chen@gmail.com</a>> wrote:<br> > Hi all -<br> ><br> > I am wondering if anyone knows the rules governing the PLT's version<br> > number? I am interested in comparing and ordering PLT's version numbers.<br> > Below are what I am aware of:<br> ><br> > before v4, the version numbers are a single integer (300 = version 3.0, 372<br> > = version 3.72)<br> > since v4, the version numbers are <major>.<minor>.<revision>, like 4.2.2,<br> > where all are numbers; and presumably this will be the case for a while<br> ><br> > Are there other rules? For example - what would be the rules for pre or svn<br> > builds?<br> ><br> > Thanks,<br> > yc<br> ><br> ><br> ><br> </div></div>> _________________________________________________<br> > For list-related administrative tasks:<br> > <a href="http://list.cs.brown.edu/mailman/listinfo/plt-scheme" target="_blank">http://list.cs.brown.edu/mailman/listinfo/plt-scheme</a><br> ><br> ><br> </blockquote></div><br>