MB>
  > Keith Thomson wrote in a message to Allan Mertner:
  >
  >  KT> And you really should use 32 bit if you are going to do ASM in
  >  KT> os/2, 16 bit ASM in a 32 bit memory model is, as i said
  >  KT> earlier, Unstable.
  >
  > Why is 16-bit code unstable in a 32-bit segment?
MB>

  Allan maintains that Virtual Pascal's support for all of the non-Pascal
  features of Borland Pascal, such as direct access to memory, is a major
  feature, and an advantage over Speed Pascal, which implements a more
  "standard" Pascal.

  Whereas Keith is arguing that those features aren't worth beans, since
  any DOS program that writes directly to memory is going to require a
  severe overhaul when being ported to OS/2, as you simply don't do things
  that way in OS/2.

  Keith has a fair point.  It's certainly the case in C++ that porting a
  DOS program so that it works in OS/2 protected mode means rewriting all
  code that does direct memory access and the like.  It's almost always
  the case that the rewritten code ends up being written in "standard"
  C++, using the system API to do the low-level dirty work.  I imagine
  that the situation for Pascal programs is little different.

  > JdeBP <
___
 X MegaMail 2.10 #0:

--- Maximus/2 3.01