🚀 go-pugleaf

In article <9042@hub.ucsb.edu>, spinrad@rigel.ucsb.edu writes:
> Originally I wrote an article which described that I had problems with printf
> from a TSR written in MSC.  I got many responses which said that this was 
> a reentrantcy problem.  Believing that I correctly handled the reentrancy
> issue, I wrote an assembly language routine which invoked int 21
> print string. I used this function instead of using MSC's printf in my
> TSR and everything worked fine.  Thus the problem was due to printf
> and not to reentrancy.

I would hazard a guess that your INT 21H call was the one with AH-9. Low
numbered calls tend to work OK (whether they're actuallty re-entrant or
use a different stack I'm not sure). printf almost certainly uses the
UNIX-style 'write' call which is around 40H (don't have the docs here).

Why not write your own printf, using a fixed buffer and vsprintf? Then output
the generated string with INT 21H AH=9?
-------------------------+-------------------------------------------------
Bob Eager                | University of Kent at Canterbury
                         | +44 227 764000 ext 7589
-------------------------+-------------------------------------------------