Dear Prof. Ripley:
Please excuse: I keep peeling the onion and finding another
question: Is it correct to infer that S-Plus 2000 itself never gave you
any trouble, and the only problems you had was with code you had written
yourself in some other language and had used via either dyn.load() or
dll.load()? Moreover, you got dll.load() to work with code compiled
using Visual C 6, though it may not always have been straightforward?
Thanks again.
Spencer Graves
Prof Brian Ripley wrote:
On Thu, 17 Feb 2005, Spencer Graves wrote:
Dear Prof. Ripley:
As I reread your answer, I find I'm not completely certain
about one point: Is it correct to say that previously compiled code
ran for you, but when you needed to compile something, you needed to
use a more modern compiler?
Indeed, it was the compiler itself that would not run. That meant
that dyn.load() was not available to us, but dll.load() using VC6
worked (if tediously).
Thanks again.
Spencer Graves
Prof Brian Ripley wrote:
The only problem we found was that the Watcom compilers we used to
compile for S-PLUS 2000 did not run under XP. They were
discontinued long ago, and we probably did not have the final versions.
Otherwise we ran quite extensive tests using S-PLUS 2000 under
Windows XP until late 2003, and saw no difference from Windows 2000.
On Wed, 16 Feb 2005, Spencer Graves wrote:
Does anyone have experience running S-Plus 2000 under Windows
XP? Our company is planning to upgrade operating systems to Windows
XP, and we'd like to know if this change might break some of our
legacy applications that we'd prefer not to have to migrate from
S-Plus 2000 to S-Plus 6.1 or 6.2. Insightful just told me that
S-Plus 2000 "does run under Windows XP but has not undergone
extensive testing and is not supported under Windows XP."
|