version and versions; upgrade and upgrades
Anyone who uses Python 2.5 who has a Zope Plone CMS running on Python 2.4 will understand. Or anyone force to retrieve TCL 8.3 DLL’s when TCL 8.4 will not do … or who is advised to look for the correct version of Perl for some neglected custom add-on… will understand this. I will not comment on some Java nightmares I have known or the worst Microsoft howlers. I am talking about those ‘harrowing’ “I wish I hadn’t upgraded” experiences.
|| ===== begin of program ========
{curl 3.0, 4.0, 5.0 applet}
Hello World!
|| ======end of program ========
This is a Curl Surge banality which declares that we are happy with all likely versions of the Curl Surge RTE available to your browser.
But what if you had upgraded to version 4.0 and had loaded a 3.0 apple such as
{curl 3.0 applet}
Hello World!
Would you suddenly have version issues?
No.
I have a note on this in a post on Rebol (“… unexpectedly he yells, ‘the Rebels are coming!!’, but no one is listening … ”
There is something comparable in Cincom VisualWorks Smalltalk where a simple text file is used to declare at runtime which version of the runtime environment to launch for a given Smalltalk bytecode image.
Here is what my Curl Control Panel tells me:
Curl® Runtime Environment
Build: 5.0.2
Supported API Versions: 5.0.2, 4.0.4, 3.0.10
Debuggable API Versions: 5.0
