In a message to Paul West  Allan Mertner wrote:

AM> 4) {$I-} is not a compiler directive, but a statement.  Instead of
AM> instructing the compiler to generate different code, it simply causes
AM> a "RaiseIOError := True" statement to be inserted in the code.  This
AM> means, that it cannot be used outside Begin..End blocks, for example
AM> in the beginning of a unit.  It also means that the state of I/O
AM> checking can be changed by Pascal code, as in the example:
AM>   {$I-}
AM>   Reset(f)
AM>   ...
AM>   If x = 0 then Exit;
AM>   {$I+}
AM>
AM> If x is 0, the I+ statement is never executed.  Sad.

OUCH!

That explains some problems I was having porting some of my older utility
routines over.   It's a serious problem with compatability, but for new
code, as long as you are carefull, shouldn't be a real problem.

AM> Text-mode apps written in SP require a 27kB DLL KBDVIO32.DLL to run.
AM> This is because SP not supports thunking calls to 16-bit API
AM> functions - and all of the text-mode Vio, Mou and Kbd calls are 16
AM> bit.  The DLL is written in C and cannot be written in Speed-Pascal.
AM> If you want to access other 16-bit API calls, you need to write
AM> another thunking DLL for it - but not in SP...

Now that could be a real problem.  If I have to write stuff in C to get
Speed �up and running, I may as well write C in the first place.

I guess I'll have to take another look at VP.  I was hoping SP would be the �answer.

... For sale: Hourglass for timing Windows.
--- JMail-G 2.80c