<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
To reduce confusion between PLaneT "package versions" and the version
numbers of software packages that happen to be packaged as PLaneT
packages... I'd like to strongly suggest that instead of having the
PLaneT Web pages say this:<br>
<br>
<blockquote><tt>Package</tt><br>
<tt>version Version<br>
</tt><tt>1.1 0.3</tt><br>
</blockquote>
<br>
that they instead say this:<br>
<br>
<blockquote><tt>Package</tt><br>
<tt>version Version<br>
</tt><tt>(1 1) 0.3</tt><br>
<br>
</blockquote>
Basically, I want to never, ever see "." in a PLaneT package version
number. "." is already used in the version numbers of most software
packages ever written, which means it terrific for distinguishing the
two kinds of version numbers. TThe sexp format proposed above is also
a good mnemonic for the "Scheme" flavor of version number, as opposed
to the "normal" flavor. The sexp format also fits the different ways
that PLaneT package version numbers are used, better than a string with
dots in it would, and "require" forms don't use dots anyway.<br>
<br>
If someone could make this change, I also suggest clearer
terminological conventions, such as saying either "PLaneT Version" and
"Software Version", and never simply saying "version". Or invent a new
word for "PLaneT version" -- something like "verid", which can be
selected in "require" forms and such by a "verspec" form, only perhaps
not so dorky-sounding.<br>
<br>
I think I suggested this before, but I don't recall seeing a rationale
for doing it the current way.<br>
<br>
<div class="moz-signature">-- <br>
<a class="moz-txt-link-freetext" href="http://www.neilvandyke.org/">http://www.neilvandyke.org/</a>
</div>
</body>
</html>