RE: [MiNT] analysing syscall.spp

["Julian Reschke" <reschke@muenster.de>]

> From: owner-mint@fishpool.com [mailto:owner-mint@fishpool.com]On Behalf
> Of Jörg Westheide
> Sent: Thursday, April 15, 1999 11:26 AM
> To: mint@fishpool.com
> Subject: [MiNT] analysing syscall.spp
>
>
> Hi Konrad!
>
> KK>In this case it doesn't hurt anything as long as they're atomic.
> Yes, but that has to be ensured
>
> KK>Anyways, Malloc() or Mxalloc() rather :-) cannot wrap back to trap
> KK>handler, so it doesnt matter if they modify globals or not.
> Well, I thought that one aim is to make the MINT-GEMDOS reentrant and
> callable from interrupts (where possible)
>
> KK>Contrary, a Fopen() can wrap back if a filesystem driver decides to
> KK>call a trap.
> I don't like think that idea because we then will never be able
> to remove the
> rentrance check.
> Wasn't there an interface for these drivers to call MiNT directly? If so
> these calls are no problem. Programs hooked in the GEMDOS chain
> before MiNT
> currently should be no problem (as long as they do not do GEMDOS calls via
> trap#1 again). For calls to programs behind MINT one could introduce a new
> call which bases on trap_1_emu. But that means that you have to decide if
> this system extension has to be started before or after MiNT... :-/

I really don't grasp why this is such a big problem... Under MagiC
everything is reentrant and still callable using the traps...
--
Julian F. Reschke (mailto:reschke@medicaldataservice.de)
MedicalData Service GmbH Münster, Germany