🚀 go-pugleaf

In article <17135@cbmvax.commodore.com> jesup@cbmvax.commodore.com (Randell Jesup) writes:
>	Won't work.  A message usually has pointers to other areas of
>arbitrary memory, or has an extended structure (ala StandardPacket), etc, etc.
>As has been discussed before, MEMF_PUBLIC can't be used since each person
>has had a different idea as to what should be public and what shouldn't.

  Ahhh, true. I spoke before thinking there.

>	A better idea.  You _could_ allow segments of code from a loadfile
>to be protected (at least without many problems), and you could allow 
>applications to request protected memory.

  Could you then please consider myself begging for such a feature? Such
programs as Enforcer are great for develop-time, but if we can add some
cover-the-user's-butt type of capability to all NEW programs it is a big
plus in my mind. I mean, Why should my perfectly innocent program get
spammed by DeluxePaint3? If I can protect the OS from my mistakes, and
have my program be protected from the mistakes of others, I can sleep
a little better, eh?

>Randell Jesup, Keeper of AmigaDos, Commodore Engineering.

  What exactly does 'Keeping' AmigaDos entail anyway? ;)

    Chris - Xenon


-- 
#define chanson Christopher_Eric_Hanson || Lord_Xenon || Kelson_Haldane 
I work, but you don't know who I work for. And they don't know I'm here.
"Someone thinks of us, therefore we are."