Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!uakari.primate.wisc.edu!aplcen!boingo.med.jhu.edu!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.sys.apple2
Subject: Re: Rom01 vs rom03
Message-ID: <14741@smoke.brl.mil>
Date: 14 Dec 90 21:15:08 GMT
References: <1990Dec13.090059.21608@nntp-server.caltech.edu> <14731@smoke.brl.mil> <1990Dec14.061231.1470@nntp-server.caltech.edu>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 16

In article <1990Dec14.061231.1470@nntp-server.caltech.edu> toddpw@nntp-server.caltech.edu (Todd P. Whitesel) writes:
-gwyn@smoke.brl.mil (Doug Gwyn) writes:
->In article <1990Dec13.090059.21608@nntp-server.caltech.edu> toddpw@nntp-server.caltech.edu (Todd P. Whitesel) writes:
->>> Newer versions offer features that older versions
->>>didn't, so if an application depends on such new features it will fail
->>>if you try to execute it using an old System Disk.
->>Not if you check first by calling GetVersion ($202A).
->Why, does calling GetVersion somehow magically make missing "future
->features" appear?  Wow, what an operating system!
-Very funny. I was referring to the fact that GetVersion allows the application
-to put up a nice box saying "yuck! you're still using System 3.0! Go Get 5.0.4
-or something even more recent! (OK)" instead of just barfing.

I think most of us would consider that such behavior constitutes
failure of the application under that version of the system disk.
Remember what the original question was.