Path: utzoo!attcan!telly!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!abvax!iccgcc!klimas
From: klimas@iccgcc.decnet.ab.com
Newsgroups: comp.os.os2.programmer
Subject: Re: OS/2 2.0 APIsDOWN
Message-ID: <807.26e7aa93@iccgcc.decnet.ab.com>
Date: 7 Sep 90 19:11:31 GMT
References: <1990Sep4.130929.16442@sun1.ruf.uni-freiburg.de> <4274@tuminfo1.lan.informatik.tu-muenchen.dbp.de> <20157@well.sf.ca.us>
Distribution: comp
Lines: 14

In article <20157@well.sf.ca.us>, feustel@well.sf.ca.us (David Alan Feustel) writes:
> I suspect that there may be some interest in writing OS/2 applications
> using the 1.2 APIs but running on OS/2 version 2.0 since the memory
> management and debugging is (IMHO) better with the 1.2 API. This is
> only true for small applications or applications that can be
> decomposed into small programs where the 64k segments don't cause too
> much aggravation.
> 
> Unfortunately, the 1.2 emulation of version 2.0 is not yet perfect;
> Smalltalk V/PM runs fine on IBM OS/2 v1.2 but dies immediately when
> run on the MS OS/2 v2.0.
	I believe the folks at Digitalk are aware of the incompatibility
	and are preparing an OS/2 2.0 compliant version of Smalltalk/V-PM
	for release (shortly?).