From: William Harold Newman <william.newman@ai...> - 2006-06-06 02:45:06
have drifted out of date with sbcl-0.9.13 release.
I work fairly hard to avoid manually updated data that I must update
myself directly, or manually updated data that have a nontrivial
potentially-buggy relationship to the data they depend upon. I do rely
on manual updates occasionally --- e.g., manually tweaking version.lisp-expr
seemed tolerable to me, and simpler and more robust than any automatic
CVS hack I knew how to do, and y'all and I have been tolerating it for a
long time. For this web page versioning, the dependency is trivial
and someone has been motivated to keep on updating it magically, so it's
a nonproblem; for *me* it almost looks like automatically updated
data...:-) But if the maintainer gets tired of manually magicking it,
a replacement in Classic Documentation OAOO Style might be
something like "the most recent released version of SBCL is available
for download from <a>the SourceForge File Releases system</a>,
and bleeding edge development snapshot are available by
<a ..>anonymous access to our CVS repository</a>.
William Harold Newman <william.newman@...>
PGP key fingerprint 85 CE 1C BA 79 8D 51 8C B9 25 FB EE E0 C3 E5 7C
Ubi saeva indignatio ulterius cor lacerare nequit. -- Jonathan Swift's epitaph
William Harold Newman <william.newman@...> writes:
> have drifted out of date with sbcl-0.9.13 release.
Yeah. I actually did update my working copy of the lisp->html thing,
and generated the new website about a week ago, only to find that ssh
access to the shell server was offline. Then, of course, I forgot
The site is now updated; while I don't promise not to get tired of
magically updating these dependent fields, for the moment
straightforward human frailty is more likely to cause the sparkle to
fail to perform...