TS>> of course my code is full of these System.xxx variables. It's hard to
 TS>> try to convert these to work with SP.

TS> Don't you use an editor with global search/replace?

Yes, but it's hard to convert all variables right. For example, the Val
function, how should I use it? Virtual Pascal code:

=== Cut ===
{$ifdef os2} uses use32; {$endif}

var str: string;
    num,err: integer;

    f: file;
    readed: word;

begin
  str:='5';
  val(str,num,err);

  assign(f,'myfile');
  reset(f);
  blockread(f,str,256,readed);
  close(f);
end.
=== Cut ===

Works fine compiled with Borland Pascal. Works fine compiled with Virtual
Pascal. If I wanted to make that with Speed Pascal, I would have to do it
like this:

=== Cut ===
var str: string;
    num,err: integer;

    f: file;
    {$ifdef os2}
    readed: longint;
    {$else}
    readed: word;
    {$endif}

begin
  str:='5';
  val(str,num,err);

  assign(f,'myfile');
  reset(f);
  blockread(f,str,256,readed);
  close(f);
end.
=== Cut ===

That {$ifdef} for all blockread and blockwrite variables, awful. Or if I make 
Use32 unit like in VP (contains 'type word = longint'), SP complains in 'Val' 
commands... So, two main reasons what are better in VP: system.xxx works, and 
Val command uses form val(string, number, longint). Very easy to use same
code in BP and VP.

 - Timo/2 (Using SkyReader/2)

--- Concord/BW POO1C3 (Eval.)