Am 27.03.2016 um 04:01 schrieb Cousin Ricky:
> Some months after I uploaded TiltedTorus 2.0a, I looked back on one of its
> features in horror.  In order to invoke the Sturmian root solver in
> TiltedTorus_Lathe(), I used a global parameter, rather than a macro argument!
> If I'd submitted this module as an assignment in one of my computer science
> classes, I'd get 20 points deducted just for that.
...
> This is easily fixed, but it would do something that I've never done in an
> Object Collection update (save AndroidRobot[1]): break older scenes.
> 
> Should I do it?  Older scenes could be quite easily updated, and I don't suppose
> many such scenes even exist.  I created this module in response to a request in
> p.general, and the OP ended up not using it anyway.

Version numbering best practices (such as the "semantic versioning"
scheme) would suggest that you call the new include file "TiltedTorus
3.0" (the major version number increment indicating backward
incompatibilities), and archival best practices would suggest that you
upload it as a new file, rather than replacing the old one. This way,
anyone who for some reason cannot or does not want to change their scene
can still get hold of a compatible include file.

Post a reply to this message