Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!comp.vuw.ac.nz!actrix!templar!jbickers
From: jbickers@templar.actrix.gen.nz (John Bickers)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: 8-bit death
Message-Id: <3686.tnews@templar.actrix.gen.nz>
Date: Tue, 13 May 1991 06:47:37 GMT
References: <3335.tnews@templar.actrix.gen.nz> <1991May10.000135.7550@NCoast.ORG> <3636.tnews@templar.actrix.gen.nz> <1991May12.180515.20191@NCoast.ORG>
Organization: TAP, NZAmigaUG.

Quoted from <1991May12.180515.20191@NCoast.ORG> by allbery@NCoast.ORG (Brandon S. Allbery KF8NH):

> Do *which* sort of thing?  One interrupt for the OS entry point?

    _Any_ interrupts for an OS entry point. The library approach in the
    Amiga seems faster and more powerful to me. More natural. :)

> That's probably because it potentially has even more possible values than you
> have interrupts.  Should MS-Doesn't ever break the 256-syscall barrier (this

    Yes, there's no doubt that the entry point can fan out ad infinitum
    once you're through it (like the ah could be set to something
    currently reserved, and some other register could be loaded with
    16 bits of info, so it'd branch off ah, then branch off bx, or
    whatever. And so on...).

    The thing is, why do it like this, when you could jump straight (or
    almost straight, counting the little detour to give people an
    opportunity to intercept OS calls) into the OS?

    As for not using the other interrupts (0x10 for video, etc)... ha. :)

> ++Brandon
--
*** John Bickers, TAP, NZAmigaUG.        jbickers@templar.actrix.gen.nz ***
***         "Endless variations, make it all seem new" - Devo.          ***